Skip to main content

Users, Groups, and Workspaces

A user identity establishes who signed in. Group membership supplies authorization claims. A workspace, called a site in the API, defines the document and configuration scope. Creating one of these does not automatically create the others.

Provision users​

In Administration → Users & Groups, choose Add New User, enter the email, and complete the account setup flow. Directory-backed API operations include GET /users, POST /users, GET /users/{username}, and the supported user-operation endpoint for account changes. See Manage Users and Groups for request examples.

For SSO, manage authentication and upstream membership in the identity provider and configure the appropriate group mappings. A Contract Management employee/contact record is application data, not a login account. Do not fabricate Cognito users just to populate an owner dropdown.

Grant access deliberately​

  1. Create or identify the group that represents the intended permission set.
  2. Add the user to the group, or supply the corresponding SSO claims.
  3. Grant that group access in Administration → Workspaces → Group/Role Permissions.
  4. Test with that user's actual session, including an operation that should be denied.

In defined-site-permission deployments, creating a directory group alone grants no workspace access. Automatic group/site modes behave differently; check the deployment's SitePermissions parameter before importing a group naming convention. Admins is a privileged platform group and should not be used for ordinary contributors.

Roles such as READ, WRITE, or GOVERN are not a shorthand for every management permission. User management and system management have dedicated permission families. See API Permissions.

Narrow access within a workspace​

Folder permissions can restrict content access after site authorization. Once a folder has entries, ordinary unlisted roles are denied content access; administrator/governance exemptions and the v1.19.2 metadata limitation are documented in Folders.

Experience settings can hide an action or tab for a group. They do not change what a direct API request permits. Use backend policies or separate sites for security isolation.

Disable, revoke, and remove​

Disable an account when sign-in should stop, remove unneeded group/site grants, revoke or rotate integration keys, and end sessions as appropriate. Treat these as separate operations. A JWT may remain usable until its expiry depending on how the API validates it; disabling a user is not a guarantee that every previously issued token, presigned URL, or external signing session is immediately invalidated.

Prefer disabling over deleting when you need to preserve an identifiable audit history. Before deleting an account, retain required evidence and review ownership, pending reviews, delegation, notification addresses, and identity-provider provisioning rules that could recreate it.

See Authentication, Sessions, WAF, and CORS for token lifetimes and operational checks.