Skip to content
Feature_09

The right access for your team, your agency and
Claude

Your identity provider decides who gets in, the activity log records what each person did, including through Claude, and anyone removed from your directory loses access the same minute.

Workspaces that isolate data, roles defined by a super admin, required two-factor authentication, single sign-on with Entra ID, Okta or Google, SCIM provisioning, an activity log, and your own domains with automatic TLS.

The problem

Many hands on the brand and no record

Marketing, branches, outside agencies and now AI assistants all touch what the institution publishes. In many tools anyone with access can edit or share, passwords get sent by email, and the account of someone who quit stays active for weeks. When compliance asks, the answer ends up being a search through the team chat.

0
Passwords set by an admin
3
Break-glass accounts under required SSO
5
Tries before a share link locks
0
Per-user fees
How it works

Controls your IT team can review

Isolated workspaces and roles

Each brand, market or company in the group gets its own workspace, with its own data, domains, themes, analytics and users. A super admin decides what each role allows; sharing with other workspaces, creating share links and assigning roles are separate permissions.

MODULE_ID: RBAC

Required two-factor authentication

A super admin requires two-factor sign-in across the whole account, with a grace period and reminders. After the deadline, anyone without a second factor can't reach the panel, and their API tokens and Claude connections stop working. People use an authenticator app or passkeys.

MODULE_ID: AUTH_2FA

Single sign-on

Your people sign in with their Microsoft Entra ID, Okta or Google Workspace account, and your identity provider handles passwords and MFA. SSO can be required on your domains, with up to three break-glass accounts that alert the other super admins every time one is used.

MODULE_ID: SSO

SCIM and instant suspension

With Entra ID or Okta, anyone disabled in your directory is suspended in linkable.id immediately: signed out everywhere, with their tokens and Claude connections stopped and their work kept. Directory groups can set workspaces and roles.

MODULE_ID: SCIM

Activity log

Records who did what and when. Anything done through Claude appears under the name of the person who asked for it, marked as done via Claude.

MODULE_ID: ACTIVITY_LOG

Your own domains

Connect your domains with DNS validation and an automatic TLS certificate. A domain can be shared with other workspaces, and it can't be deleted while links, pages or sites depend on it.

MODULE_ID: CUSTOM_DNS

What IT and compliance usually check

01

An agency with limited access

Invite the agency to a workspace with a role that edits pages but can't share with other workspaces or create share links. Its people sign in with email, password and two-factor, even when the rest of your institution uses SSO.

02

When an employee leaves

With SCIM, disabling them in your directory is enough. Without it, a super admin suspends them in one click: they're signed out everywhere and their work stays in place.

03

Integrations with expiring tokens

Your CRM or scripts call the public API with tokens limited to one workspace and to the permissions of whoever created them, expiring after 30, 90 or 365 days. A super admin sees every token and can revoke any of them.

04

Claude with clear limits

Claude works with the permissions of the person who connects it. Changes it makes to themes, Brand Vault values or widgets on pages that are already public go live immediately. For strict control, give those people a role without those permissions.

Direct_Answers

Frequently asked questions

Yes. A linkable.id super admin can require two-factor sign-in across the whole account, with a grace period of up to 30 days. After the deadline, anyone without a second factor can only reach the setup screen, and their Claude connections and API tokens stop working. People get an email whenever a factor is added to or removed from their account.

Yes. linkable.id connects through OpenID Connect to Microsoft Entra ID, Okta or Google Workspace. When your identity provider requires MFA, an SSO sign-in counts as two-factor. SSO is included in Corporativo and Grupo and is an add-on for Negocio.

With SCIM and Entra ID or Okta, disabling them in your directory suspends them in linkable.id immediately: they're signed out, their API tokens and Claude connections stop, and their work is kept. Without SCIM, a super admin suspends them from the user list with the same effect.

In the linkable.id activity log, which records what was done, when, and by whom. If a change was made through Claude, it appears under the name of the person who asked for it, marked as done via Claude.

No admin ever sets a password in linkable.id. Accounts are created by email invitation and each person chooses their own; password resets also arrive by email. With SSO, your identity provider handles the password.

Yes. linkable.id validates your domain through DNS and issues the TLS certificate automatically. A domain can be shared with other workspaces and stays protected: it can't be deleted while links, pages or sites depend on it.

Does your IT team need to review the controls before deciding?

We'll walk through roles, SSO, two-factor authentication and the activity log in a test workspace, and answer your security team's questions.

Request a demo