Skip to main content

​
Overview

Once you open a workspace in admin, Tessact keeps the job focused on four sections:
  • General
  • Members
  • Library
  • Limits
This is the core operating model for workspace-level administration.
Workspace admin surface

Workspace admin surface with the core section tabs

​
What Each Section Is For

The structure is intentionally narrow. Admins should not need to hunt through unrelated settings to manage a workspace safely.

​
How To Approach A Workspace Review

1

Confirm what this workspace is

Start with General so you can verify the workspace name, logo, and basic behavior settings.
2

Review who has access

Open Members to inspect the current cohort, workspace roles, and recent activity.
3

Check workflow behavior

Use Library when status visibility or status design affects how teams track work in this workspace.
4

Finish with capacity and policy

Use Limits to review storage pressure and whether the workspace should stay capped or unlimited.

​
When To Stay At The Workspace Level

Stay in workspace admin when:
  • the question is about one workspace’s identity or behavior
  • the concern is about member fit, not org-wide role design
  • file-status behavior is specific to one workspace
  • storage review needs workspace-level context
Go back to the org-level admin directory when the issue affects many workspaces at once.

​
Best Practices

  • Review the workspace in section order instead of changing settings ad hoc.
  • Keep identity, access, library policy, and limits conceptually separate.
  • Use the workspace surface for local decisions and the admin root for org-wide ones.

​
Next Steps

Workspace branding and identity

Go directly into the General section and the settings it exposes.

Status systems and limits

See how library status design and capacity policy fit together.