Company sign-in lets your company's Okta sign your team in to AdWhispr inside Claude. Nobody creates an AdWhispr account or types a password. Once it is set up, anyone at your company who has their work login and has been given access in Okta can use AdWhispr in Claude, on your team and your plan.
What you need. An AdWhispr Agency plan, with the owner account on your company email address (not a personal mailbox). A Claude Team or Enterprise plan whose people sign in through Okta. And an Okta admin who can add apps and turn on Cross App Access.
How it works
When someone on your team uses AdWhispr in Claude, Claude asks your Okta to vouch for them. Okta sends AdWhispr a signed note saying who the person is, and AdWhispr checks it before letting them in. There is no AdWhispr sign-in screen and nothing to approve: the person's work login is the key.
A few rules keep this safe:
- Only your company's Okta is trusted for your company. You tell AdWhispr which Okta address is yours, and AdWhispr ignores any other.
- You prove you own your email domain. A record in your domain's DNS settings shows the company is really yours. Only people whose work email is on that same domain get in: if the owner account is jane@yourcompany.com, it is everyone at yourcompany.com.
- The owner signs in first. Setup only finishes when you, the account owner, sign in once through Okta yourself.
- You stay in control. Turning company sign-in off, or removing it, signs everyone out of it at once.
Step 1: Start the setup in AdWhispr
Signed in as the account owner, open Settings in the dashboard and find Company sign-in, below Team. Click Set up company sign-in.
Enter your Identity provider issuer URL. For Okta this is your organization's address, for example https://yourcompany.okta.com. If your company uses a custom sign-in domain in Okta, use the issuer shown in your Okta authorization server settings. Click Save.
The card then shows three steps, with a check mark next to each one as it is done.
Step 2: Prove you own your email domain
The card shows a Host and a Value for your email domain, the one on your owner account. Add them as a TXT record at your DNS provider (where your domain's settings live, such as Cloudflare, GoDaddy or Google Domains):
| Field | What to enter |
|---|---|
| Type | TXT |
| Host or name | The Host from the card, for example _adwhispr-challenge.yourcompany.com |
| Value | The Value from the card, starting with adwhispr-domain-verification= |
Then click Check now. DNS changes can take a few minutes to appear, so if the check does not pass at first, wait and try again. Keep the record in place afterwards: AdWhispr checks it again every day, and company sign-in stops working if it disappears.
Step 3: Add AdWhispr in Okta
This step is for your Okta admin. The card lists the values to copy:
| On the card | What it is |
|---|---|
| Issuer and audience | https://adwhispr.com |
| Resource | https://adwhispr.com/api/claude/mcp |
| Claude client ID | https://claude.ai/oauth/mcp-oauth-client-metadata |
| Claude Code client ID | https://claude.ai/oauth/claude-code-client-metadata (only if your team also uses Claude Code) |
In the Okta Admin Console:
- Create an app for AdWhispr. Go to Applications, then Applications, and create an app integration named AdWhispr. AdWhispr is not in the Okta Integration Network yet, so it is a custom app.
- Turn on Cross App Access for it. Open the AdWhispr app, go to Machine Assignments, and select the Callers tile. Click Edit next to Cross App Access (XAA), select Enable, and enter
https://adwhispr.comas both the Issuer URL and the Audience. Add the scopesreadandwrite. Click Save. - Connect Claude to AdWhispr. Go to Directory, then AI agents, and open Claude. On the Resource connections tab, click Add resource connection, pick the AdWhispr app, and enter the Claude client ID from the card as the client ID and the Resource from the card as the resource identifier. Allow the
readandwritescopes, then click Add. - Give your team access. Assign the people or groups who should use AdWhispr to the AdWhispr app.
Okta's screens change from time to time. If yours look different, Okta's own Cross App Access guide has the current steps; the values from the card stay the same.
Step 4: Turn on AdWhispr in Claude
In your Claude admin settings, add AdWhispr as a connector for your organization and choose to have it use your company sign-in through Okta. Claude's admin console walks you through this part.
Step 5: Sign in once yourself
Open Claude with your work login and ask AdWhispr anything, for example Who are my competitors? That first sign-in, by you as the owner, confirms the setup. The card then shows company sign-in as Live, and your team can start using AdWhispr.
What your team sees
Your team opens Claude, asks AdWhispr a question, and gets an answer. There is no sign-up and no extra login.
Each person who signs in this way:
- Gets an AdWhispr account automatically, on your team and your plan. Tracked brands, agent calls and creative credits are shared with the team, just as with an invited teammate.
- Already has an AdWhispr account on their work email? Invite them to your team first (Settings, then Team). Company sign-in then uses the account they already have. Without the invite they are asked to sign in the usual way, so nobody's existing account is taken over.
- Shows in your team list with a Company sign-in badge.
- Cannot leave the team on their own. Your company decides who has access, through Okta.
Ad accounts each person connects stay theirs alone, and their chats stay private.
Seats
Company sign-in includes 10 seats, separate from the seats you use for email invites. The card shows how many are in use. When the seats are full, the next person is refused until a seat frees up. Need more? Email hello@adwhispr.com.
Turn it off or change it
- Turn it off. Use the switch on the card. Everyone signed in through Okta is signed out at once, and nobody new can sign in until you turn it back on.
- Change your Okta address. Click Change next to the identity provider. This starts setup over: the domain check and your own sign-in are needed again, and everyone is signed out in the meantime.
- Remove it. Click Remove. Company sign-in is deleted and everyone signed in through it is signed out.
If something does not work
- The card says your account is on a personal mailbox. Company sign-in needs the owner account on your company email address. Change the email on your AdWhispr account, then try again.
- The domain check does not pass. Make sure the record is a TXT record, the host and value match the card exactly, and give DNS a few more minutes.
- Someone is refused when they sign in. Check that their work email is on your proven domain, that they are assigned to the AdWhispr app in Okta, and that a seat is free. If they already had an AdWhispr account, invite them to your team first.
- The card says another organization has already connected this identity provider. Email hello@adwhispr.com and we will sort it out.