WolfSuiteWolfXLWolfPPTWolfDocxWolfRender

WolfSuite Workspace · Documentation

Roles: people, agents, guests and administrators

Wolf Workspace decides what each participant may do from what kind of participant it is: a person, an agent acting for a person, or a guest invited to specific documents. On a hosted account, administrators also manage every agent token. 1 2 3

At a glance

ParticipantReadsProposesSaves or approvesEvidence
Person (member)Every document in the roomYesYes: saves directly, approves and rejects proposals, restores revisions 4 5
AgentEvery document in the roomYes, with doc_editCan save with mode: "commit"; never approves, rejects or restores 6 7 1 8
Guest who may proposeOnly its documentsYes, and commentsNo 2 9
Guest who may only viewOnly its documentsNoNo 10

Agents

An agent cannot approve or reject a proposal, its own or a person's. The attempt is refused with FORBIDDEN and nothing changes. 1 11

An agent cannot restore an earlier revision, but it can read one. 8 12

An agent acting for a guest has the same document limits as that guest. An agent acting for a member does not inherit any guest limit. 13

When the workspace has no seat for an agent, the agent is refused doc_read and workspace_list and does not take a seat. 14

Guests

  • A guest sees only the documents it was invited to. Any other room, document, proposal or comment thread answers as if it does not exist. 15
  • A guest takes no seat, however much it reads. 16
  • A guest who may propose can comment and propose edits, and is refused a direct save and a decision on any proposal. 2 9
  • A guest is refused new rooms, uploads, exports, packs and share links, each with 403 FORBIDDEN. 17
  • The web app hides the New document controls from guests. 18

Seats

A workspace at its seat limit still serves participants who take no seat, and refuses one more member. 19

A participant without a seat can still create a room. 20

Administrators and members of a hosted account

An administrator sees every agent token on the account. A member sees only its own. 3

Each agent token name is unique among the account's tokens that are not revoked, and becomes available again once its token is revoked. 21

Evidence

Each numbered reference above points to the test that exercises the statement or to a recorded observation of the hosted service at workspace.wolfsdk.com. Test paths are relative to the WolfSuite repository.

  1. Test sdk/web/packages/server/test/ws.test.ts: “an agent that sends proposal.decide gets FORBIDDEN, for its own proposal and for a user's; nothing changes for anyone”
  2. Test sdk/web/packages/server/test/scoped.test.ts: “proposes an edit to its document and comments on it, but cannot commit or decide”
  3. Test sdk/web/packages/control-plane/test/account-routes.test.ts: “a member is told it sees its own tokens, an administrator that it sees every token”
  4. Test sdk/web/packages/server/test/rooms.test.ts: “approve commits the proposal's batches under its id, by its author, and announces in order”
  5. Test sdk/web/packages/server/test/revert.test.ts: “makes the old bytes the head as a new revision, written by the user, and announces it as a commit”
  6. Test sdk/web/packages/mcp/test/tools.test.ts: “lists the documents with their heads and what is open on them”
  7. Test sdk/web/packages/mcp/test/tools.test.ts: “commit applies the ops at once and reports the new head and the log entry”
  8. Test sdk/web/packages/server/test/revert.test.ts: “is refused for an agent, a stale head, a revision that is not below the head, and one equal to the head”
  9. Test sdk/web/packages/workspace-cli/test/guest.test.ts: “proposes an edit and is refused a commit, a decision and the assistant”
  10. Test sdk/web/packages/server/test/scoped.test.ts: “reads its document and cannot write at all”
  11. Test sdk/web/packages/server/test/rooms.test.ts: “it cannot approve its own proposal: FORBIDDEN, and the proposal, the head and the session log stay as they were”
  12. Test sdk/web/packages/server/test/revert.test.ts: “rebuilds the requested bytes without writing a commit, including for an agent”
  13. Test sdk/web/packages/workspace-cli/test/actors.test.ts: “an agent of a guest inherits the scope, and an agent of a member does not”
  14. Test sdk/web/packages/mcp/test/tools.test.ts: “an agent without a seat is refused doc_read and workspace_list, and takes none”
  15. Test sdk/web/packages/server/test/scoped.test.ts: “answers as a room, a document, a proposal or a thread that does not exist”
  16. Test sdk/web/packages/workspace-cli/test/guest.test.ts: “takes no seat, however it reads”
  17. Test sdk/web/packages/workspace-cli/test/guest.test.ts: “is refused a room, an upload, the export, the pack and a share link, each with 403 FORBIDDEN”
  18. Test sdk/web/apps/workspace/test/ui.test.tsx: “offers New document controls for members and hides them for guests”
  19. Test sdk/web/packages/server/test/seatless.test.ts: “serves a seatless user and the agent of a seatless operator, and still refuses one more member”
  20. Test sdk/web/packages/server/test/seatless.test.ts: “lets a seatless user create a room without a seat”
  21. Test sdk/web/packages/control-plane/test/agent-tokens.test.ts: “is unique among the customer's tokens that are not revoked, and free again once revoked”