Manage workspace identity and user provisioning

The Identity page in workspace settings is where owners and admins control how your team signs in to Vibely and how they join the workspace. It brings together domain verification, single sign-on (SSO), requiring SSO, and automatic user provisioning.

• Available on: Business
• Access: workspace owners and admins
• Location: Settings → Access → Identity (vibely.sh/settings/identity). The same SSO and SCIM controls also appear in Settings → Security center.

​

What’s on the Identity page

​

Verify your domain

Verifying a domain proves your company owns it. Nothing else on the Identity page works until it’s verified, and verification is what stops another workspace from claiming a domain like gmail.com.

​

Before you start

• A Business workspace, and the owner or admin role in it.
• Access to your domain’s DNS settings, or someone who can add a record for you.

​

Verify a domain

​

How domain verification works

• A workspace verifies one email domain.
• A domain can belong to only one workspace. If another workspace already claimed it, saving it fails with “already linked to another workspace”.
• Changing the domain clears its verification. You get a new record and have to verify again.

​

Troubleshooting verification

​

User provisioning

Once your domain is verified and SSO is on, people from your company can join the workspace without an invitation.

​

Role on first SSO login

When someone with an email on your verified domain signs in and isn’t a member yet, Vibely adds them to the workspace with the role you choose here: Viewer, Editor, or Admin. It defaults to Editor, which can create and publish projects, so set it deliberately. This happens on any successful sign-in by an address on your domain, not only sign-ins through your identity provider, unless you require SSO. If the person’s default workspace is a free one they own, Vibely also makes your workspace their default, so they land in the company workspace instead of their personal one. A paid personal workspace is never touched.

​

SCIM provisioning

Your identity provider can create, update, and remove members for you. Issue a SCIM token here and set the Role for SCIM users. See SCIM.

​

How provisioning methods interact

Provisioned members are managed like everyone else: they appear in People, where you can change their role or remove them.

​

Require SSO and session duration

With a verified domain and SSO enabled, you choose how strict sign-in is: You can only require SSO once the domain is verified; otherwise the workspace could lock itself out.

​

How Require SSO is enforced

Vibely checks every request from a member of an SSO-enabled Business workspace. If Require SSO is on and the member’s session didn’t come through your identity provider (for example, they signed in with a password or with Google), Vibely signs them out and sends them to the sign-in page with the message “Your workspace requires single sign-on.” They sign in again with their work email to go through your identity provider.

• The workspace owner is exempt, so they can always get back in to fix the SSO setup if the identity provider breaks.
• It applies to all of the member’s Vibely usage, not just this workspace. A member who also belongs to other workspaces has to sign in through SSO to use any of them.

​

Session duration

Session duration offers 24 hours, 48 hours, or 7 days (the default). It sets how long an SSO sign-in lasts. When a member’s SSO session is older than the setting, Vibely signs them out with the message “Your single sign-on session has expired”, and they sign in again through your identity provider. Changes to Require SSO and Session duration take effect within about a minute.

​

FAQ

​

Related