Skip to main content
Teams let a company use one ScrapeBadger balance from several user accounts. Each member signs in with their own account, and the team’s API keys draw credits from the team owner’s balance and use the owner’s rate limit. Create a team on the Teams page.

Roles

If the owner deletes their account, the team is deleted with it, including every member’s team API keys.

Member permissions

Admins grant plain members any of these: A member can always edit, view, disable and delete the keys they created themselves.

Member keys and service keys

Member keys

Belong to the member who created them. They stop working the moment that member leaves or is removed from the team. Nobody else — not even the owner — can view a member’s key.

Service keys

Owned by the team, not a person, so they keep working when people come and go. Use them for production systems. Only members with Manage service keys can view or change them.
Both kinds support notes, expiry dates, API permissions and IP restrictions, exactly like personal keys. A team key calling an API it isn’t permitted to call gets 403 insufficient_scope.

Inviting people

Admins invite by email from the team’s Members tab, choosing the role and, for members, their permissions. The invitee gets an email with a link that:
  • works only for the invited email address, on an account whose email is verified
  • expires after 7 days
  • can be revoked from the pending invitations list
Invitees can also accept from the Teams page once they’re signed in. Inviting the same email again replaces the earlier invitation.

Single sign-on (SSO)

Connect your company’s identity provider to a team, and anyone with an email on your company domain can sign in with it and join the team automatically. Any OpenID Connect (OIDC) provider works, including Okta, Microsoft Entra ID, Google Workspace and Auth0. SSO covers signing in to the dashboard only. API calls still authenticate with API keys. Owners and admins set it up on the team’s Single sign-on tab:
1

Create an app in your identity provider

Create an OIDC web application that uses the authorization code grant. You can create it with any redirect URI and update it in step 3. ScrapeBadger requests the openid, email and profile scopes.
2

Enter the app's details

Enter your email domain (for example example.com), the issuer URL (in Okta, https://<your-org>.okta.com, or your custom authorization server’s issuer), the client ID and the client secret. ScrapeBadger reads the issuer’s discovery document to find its endpoints.
3

Add the redirect URI to the app

Copy the Redirect URI shown on the tab into the app’s sign-in redirect URIs. It looks like https://scrapebadger.com/api/auth/sso/callback/sso-example-com.
4

Verify the domain

Add the DNS TXT record shown on the tab at your DNS provider, then click Verify domain:Nobody can sign in through the provider until the domain is verified. This stops anyone outside your company from putting an identity provider in front of your addresses.
From then on, people choose Sign in with SSO on the sign-in page and enter their work email:
  • New people get an account the first time they sign in, and join the team as members. Grant them permissions from the Members tab as usual.
  • Existing accounts on your domain are linked the first time their owner signs in through SSO. They can keep using their password or Google sign-in too.
  • Only addresses on the verified domain and its subdomains can sign in through it. If the identity provider returns any other address, the sign-in is refused.
A team can have one identity provider, for one domain, and a domain can belong to only one team. Webmail domains such as gmail.com can’t be used. To rotate the client secret, enter the new one on the tab. Turn off removes the connection. Members stay in the team, but anyone who only ever signed in through SSO has no password, so they’ll need Continue with Google on the same email (or support) to get back in.

Audit log

Owners and admins see an Audit log tab on the team page: a permanent, read-only record of who did what and when. Each entry shows the person who acted, the time, and the IP address it came from. Filter by category, and expand an entry to see the exact changes. Entries cannot be edited or deleted; they are removed only if the team itself is deleted.

Leaving and deleting

  • A member or admin can leave from the team’s Settings tab. Their member keys are deleted; service keys are unaffected.
  • The owner can delete the team, which immediately and permanently deletes every team key.