Administration

Workspace owners and admins use these guides to configure workspace-level administrative features.

Billing and usage

The billing page shows the current subscription status to all workspace members. Owners can view and manage billing, while admins and members see the status and a brief owner-managed notice without financial details. The credit page tracks a shared balance made up of the monthly workspace allowance, purchased credits, and any bonuses, alongside daily usage per member.

AI

AI settings control whether Epismo built-in AI may review cases billed to this home, the auto-review default for new cases, optional review guidance, and whether review may use web search. Owners and Admins change workspace settings; personal space is self-managed.

Identity and access

Playbooks and Cases have an owning User or Workspace account (ownerId), which is also the billing home. A personal owner has full rights; current Owners and Admins exercise ownership rights for a Workspace. Other members need explicit user or Team grants, or public visibility for published reads. Workspace membership alone grants no resource access. Removing a Workspace member clears their direct grants on items owned by that Workspace, including archived and completed items. If removal would leave any affected item without an explicit editor, add another User or Team editor first, including on completed and archived items. Personal and other-Workspace shares remain unchanged. Team and management authority follow current membership. Required SSO applies to members; non-member direct shares use normal Epismo authentication. Cross-Workspace Team sharing verifies the participation Workspace's SSO. Lists use explicit access and supported public visibility; ownership alone does not include an item.

Viewers can read shared content but cannot edit; Playbook drafts require editing. Editors may change content and sharing, retain at least one explicit editor when changing grants, and archive or restore. Ownership is required for affiliation transfer, maintainer changes, permanent Case deletion, and historical Playbook version archival. assignedTo expresses responsibility and never grants rights. A newly selected assignee or maintainer must already have editing access and, for a Workspace-owned resource, belong to that Workspace. Reassignment preserves sharing; ownership transfer does not automatically add the former owner as an editor.

SSO can be enabled as an additional sign-in method or marked Required after domain verification and a successful login test. When required, Workspace access needs current verified SSO evidence, including Web, CLI, and MCP credentials. Evidence expires at an absolute 12-hour deadline; refreshing or deriving credentials does not extend it. Web redirects to SSO, while CLI/MCP requests without evidence are denied and require sign-in again. Owners retain email-code recovery.

Integration setup

Workspace owners and admins install the Slack app from workspace integrations. See Slack connection setup for installation and member account connection steps.

In a workspace, an Owner or Admin must first choose Install Google Drive in Integration settings (/settings/integrations). Members can then connect their own Google accounts. Personal spaces connect directly, and personal and workspace connections remain separate. See Google Drive. Owners and Admins can also uninstall Drive or remove the Slack integration for the whole workspace from these settings.

A team can connect multiple workspaces. Only team participants who are owners or admins of their connected workspace can send, list, or revoke team invitations. The email recipient signs in with that email and chooses an existing workspace or creates one. The sender never chooses the destination. Acceptance connects the workspace and adds the recipient, not every workspace member. Accepting into a workspace already connected to the team returns HTTP 409 without consuming the invitation. Use team member management to add participants in that workspace. Each workspace manages its own participants. The same user can participate through multiple workspaces; removing their membership in one workspace preserves their participation in the others. Disconnect removes that workspace and its participants; other connections remain. Team-based access requires both the participation workspace and the resource home to stay connected. Direct user grants remain after disconnect. Invitations expire after fourteen days; resending closes the previous invitation. Connecting a workspace does not bypass its subscription requirements.