Enterprise
SSO, SCIM & team security
SAML single sign-on
- 1Settings → Team → Security → Domains: add your company domain and publish the TXT record shown (host _skrap-verification.<domain>). Press Verify.
- 2Copy the service provider details (Entity ID, ACS URL, or the metadata URL) into a new SAML app in your identity provider. Send the user's email address as the NameID or as an email attribute.
- 3Back in Skrap, paste the identity provider metadata XML or its metadata URL, or enter the entity ID, sign-in URL and signing certificate. Turn SAML on.
- 4Press Test connection. You sign in at your identity provider and come back to Settings with the result; nobody is signed in by a test.
- 5Optional: turn on just-in-time membership (people on your verified domain join the team on first sign-in, with the default role you pick) and Require SAML.
Identity provider notes
| Identity provider | Where |
|---|---|
| Okta | Applications → Create App Integration → SAML 2.0. Single sign-on URL = ACS URL, Audience URI = Entity ID, Name ID format = EmailAddress, Application username = Email. Copy the metadata URL from the Sign On tab. |
| Microsoft Entra ID | Enterprise applications → New application → Create your own → Non-gallery. Single sign-on → SAML: Identifier = Entity ID, Reply URL = ACS URL. Download Federation Metadata XML or copy the App Federation Metadata Url. |
| Google Workspace | Admin console → Apps → Web and mobile apps → Add custom SAML app. Download the IdP metadata. ACS URL and Entity ID from Skrap, Name ID format = EMAIL, Name ID = Basic Information › Primary email. |
What Skrap checks
- The Response or the Assertion must be signed with your identity provider's certificate (up to three certificates, for rotation). Unsigned assertions are refused.
- Issuer, audience (your team's Entity ID), recipient (your team's ACS URL), NotBefore / NotOnOrAfter (60 s clock skew) and assertion age (10 minutes) are checked.
- Each sign-in answers a request Skrap made in the last 10 minutes (InResponseTo), from the browser that started it, and each assertion is accepted once.
- IdP-initiated sign-in (from your identity provider's dashboard) is off by default; turn it on per team if you need it.
- The address must be on one of your verified domains, so an identity provider can never sign in someone at another company.
Require SAML and owner break-glass
With Require SAML on, members can only sign in through your identity provider: passwords, Google and Microsoft sign-in are refused, and every member is signed out once. The owner keeps a break-glass sign-in with a password (or Google / Microsoft) protected by two-factor authentication, so a broken identity provider can never lock the team out. Turning it on needs an enabled, successfully tested connection, a verified domain and the owner's two-factor authentication.
Signing in
Members useSign in with SSO on the Skrap sign-in page and enter their work email.SCIM provisioning
Create a SCIM token in Settings → Team → Security (shown once) and give your identity provider the base URL https://api.skrap.ai/scim/v2 with Authorization: Bearer scim_…. Users need an address on a verified domain. Roles come from the SCIM roles value (admin, developer, member, billing, readonly), from a group you map to a role, or the team's default.
- GET
/scim/v2/UsersList users. filter: userName, externalId, emails or id with eq; startIndex, count (≤ 200). - POST
/scim/v2/UsersCreate (or link) a user on a verified domain and add them to the team. - GET
/scim/v2/Users/{id}One user. active = on the team. - PUT
/scim/v2/Users/{id}Replace name, externalId, active, roles. - PATCH
/scim/v2/Users/{id}active (true / false, also as text), name, displayName, externalId, roles. - DELETE
/scim/v2/Users/{id}Deprovision and forget the SCIM link. - GET / POST
/scim/v2/GroupsList (filter displayName eq) and create groups. - GET / PATCH / PUT / DELETE
/scim/v2/Groups/{id}Members add / remove (members[value eq "id"]), rename. - GET
/scim/v2/ServiceProviderConfigAlso /ResourceTypes and /Schemas.
Deprovisioning
Deactivating (active=false) or deleting a user removes them from the team (they keep a Free account with their own data), turns all their API keys off, and ends every app session, browser extension and AI-app connection at once. Reactivating puts them back on the team. The owner can't be deactivated.
Session controls
| Setting | What it does |
|---|---|
| Maximum session length | 1 h, 8 h, 24 h, 7 days, 14 days or 30 days, counted from sign-in (refreshing doesn't extend it). |
| Idle timeout | 15 min to 24 h without a request from the app. An open tab that keeps polling counts as activity. |
| Sign out all members | Ends every member's sessions, extension and AI-app connections immediately (not the owner's). |
Refused requests answer 401 with SESSION_EXPIRED, SESSION_IDLE or SESSION_REVOKED; the app sends people back to sign in.
Sign-in IP allowlist
Add IPv4 / IPv6 addresses and CIDR ranges (up to 100). Members can then sign in and use the app only from those addresses; a session that moves outside gets IP_NOT_ALLOWED and works again back on the network. The owner is never blocked (break-glass). API keys keep their own per-key IP allowlist.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including billing and security settings. One per team. |
| Admin | Invites and removes members (not other admins), reads the team audit log, uses the tools, API keys and webhooks. |
| Developer | Uses the tools (spends credits), API keys and the team's webhooks. |
| Member | Uses the tools. API keys unless the owner limits the API to Owners, Admins and Developers. |
| Billing | Invoices, credits and usage. No tools, no spending, no API keys. |
| Read-only | Sees lists, results and usage. No tools, no spending, no changes, no API keys. |
A request a role can't make answers 403 ROLE_FORBIDDEN.
Audit log API
GET /api/v2/audit-events with an API key of the team Owner or an Admin returns the team audit log, newest first by default. Page with next_cursor.
| Query | Meaning |
|---|---|
limit | 1–500 (default 100) |
order | desc (default) or asc |
cursor | next_cursor from the previous page |
since / until | ISO 8601 times |
action | prefix, e.g. team. or auth.login |
actor / actor_email | who did it |
curl "https://api.skrap.ai/api/v2/audit-events?limit=100&order=asc&since=2026-11-01T00:00:00Z" \ -H "x-api-key: sk_live_…"1{2 "data": [3 {4 "id": "6736c1f0a1b2c3d4e5f60718",5 "action": "scim.user_deactivated",6 "description": "Identity provider deactivated a user",7 "actor": { "id": "scim:6736…", "email": "SCIM (Okta)" },8 "target_id": "6736b2…",9 "details": { "email": "sam@acme.com", "keysDisabled": 1, "sessions": 2 },10 "ip": "203.0.113.9",11 "user_agent": "Okta SCIM Client",12 "created_at": "2026-11-15T09:12:44.031Z"13 }14 ],15 "has_more": true,16 "next_cursor": "eyJ0IjoiMjAyNi0xMS0xNVQwOToxMjo0NC4wMzEwMDBaIiwiaWQiOiI2NzM2YzFmMCIsIm8iOiJhc2MifQ",17 "retention_days": 36518}Events
- auth.login, auth.login_google, auth.login_microsoft, auth.login_saml, auth.logout_all, auth.session_revoked, auth.2fa_enabled / disabled
- team.saml_updated / saml_tested / saml_deleted, team.domain_added / verified / removed, team.policy_changed (Google / Microsoft SSO)
- team.session_policy_changed, team.ip_allowlist_changed, team.access_policy_changed, team.members_signed_out, team.member_provisioned
- team.scim_token_created / revoked, scim.user_created / updated / deactivated / reactivated / deleted, scim.group_created / updated / deleted
- team.invite_sent, team.member_joined / removed / left, team.role_changed, team.ownership_transferred
- api_key.created / updated / revoked / deleted, webhook.*, team.audit_stream_updated / deleted
- list.exported, bulk.results_downloaded, account.data_exported, audit.exported, billing.*
Audit log streaming
New events are POSTed in batches of up to 100, oldest first, about every 15 seconds, signed like Skrap webhooks with the stream's secret (shown once; rotate it any time). Any 2xx answer moves the cursor; anything else is retried at 1 min, 5 min, 30 min, 2 h, 6 h and then every 12 h, and nothing is skipped. After 50 failures in a row the stream pauses itself; turning it back on resumes from where it stopped (the audit log keeps 365 days).
1POST https://siem.example.com/skrap2Skrap-Signature: t=1763197964,v1=5f2c…3Skrap-Event: audit.events45{6 "type": "audit.events",7 "id": "ab_9c1e…",8 "team_id": "6736a0…",9 "sent_at": "2026-11-15T09:12:50.120Z",10 "events": [ { "id": "…", "action": "team.ip_allowlist_changed", "…": "…" } ]11}1import crypto from "node:crypto";23// rawBody: the exact bytes received; header: req.headers["skrap-signature"]4export function verifySkrap(rawBody, header, secret) {5 const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));6 if (Math.abs(Date.now() / 1000 - Number(parts.t)) > 300) return false;7 const expected = crypto.createHmac("sha256", secret).update(`${parts.t}.${rawBody}`).digest("hex");8 return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1));9}Use the raw body
Verify against the exact bytes you received, before parsing the JSON.