Teams

Every rule here is off until the owner turns it on; none changes a workspace of one.

Roles

The owner changes a role under Dashboard → Settings → Members (a member.role audit row). Making a member a contractor revokes the phone passwords, browser tickets and shared-port sessions they hold on boxes they do not own, closes their tunnels to those boxes, and ends the anyone and public links they made (Share a port).

A contractor:

• sees only the boxes they created: another member's box, and its snapshots, read as not found everywhere, and a template name held by a snapshot they cannot see is 409 template_taken;
• cannot access workspace sandboxes (not found). Demotion also blocks pending sandbox changes and monitor-ticket requests that have not yet been accepted; work already accepted may finish. Sandbox requests through API keys use the member's current role, so promotion restores access within the key's permissions. Revoke an API key explicitly when it must remain invalid after a later promotion;
• lists environments and upgrades their own boxes, but creating, editing or deleting one is 403 not_allowed;
• always creates Restricted (safe for third parties) boxes, which none of your credentials reach (Safe for third parties); an API create with "restricted": false is 403 policy_denied, rule contractor_restricted;
• gets 403 not_allowed from the audit log, the members list, the policies, workspace secrets and cloud federation, and a secret only when it is granted to their box or to them.

A box belongs to the member who created it; boxes Prized creates for you belong to the owner (ownerUserId on the box object). The dashboard's Boxes page lists the boxes you own first, so a box someone else created for you is in its Team section (Dashboard: Boxes).

Policies

Dashboard → Settings → Policies: the owner edits, members read, contractors see Your role does not include the workspace policies.

• A refusal is 403 policy_denied with rule and message; the CLI prints the message (exit 5), the dashboard shows it beside the control.
• The spend cycle is the month ending at your plan's period end, or the UTC calendar month without a plan; spend counts against the box's owner.
• Waking or resizing a teammate's box checks the box owner's spend, not yours. A wake checks their box count too, refusing only when they are already over the limit. The size cap still applies to every resize a member requests; workspace owners remain exempt from these policies.
• The box limit refuses a wake only when the member is already over it. A failed launch keeps its slot until cleanup finishes, even after deletion.
• Failed-launch cleanup also reserves four hours of that box's allowance against the member's spend cap. This is not billed usage; the reservation lifts when cleanup finishes, not when the billing cycle changes.
• Under a floor, a new box with no auto-pause setting takes the floor, a box from before the floor is paused as if it had it, and a member's Auto-pause menu stops there. On the free credit the floor does not apply: only the box's own setting, or the credit's 2-hour default, counts.

GET /api/v1/workspace/policies reads the rules; changing them is dashboard-only and writes a policy.update row (API reference).

Quiet hours

Every box in the workspace, the owner's included, is paused in a daily window: start and end as HH:MM, the weekdays it applies to, the weekdays quiet all day, and one IANA timezone. A window that ends before it starts crosses midnight and belongs to the day it started on.

• A box woken inside the window stays up 15 minutes, then is paused again.
• To exempt a box, the owner marks it Exempt under Quiet hours on its box page (PATCH /api/v1/boxes/{id} with {"quietHoursExempt": true}; anyone else is 403 not_owner).

A quiet-hours pause is an ordinary pause.

Audit log

Dashboard → Settings → Audit log (Dashboard: Audit): who did what, on which box, when. Owners and members read it; contractors see Your role does not include the audit log.

Two origins

• server: the control plane saw it.
• client, shown as reported: the CLI or the box told us afterwards, because the control plane never sees a command run over ssh, a file copied, or a prompt started. A reported row is a claim by a credential in your workspace, not an observation: an offline or older CLI posts none, and nothing checks it against what ran.

Once deletion begins, new client reports for that box are refused; existing rows remain in the log.

Every row names the member (actorUserId) and the credential that acted (actorTokenId); browser terminal and phone sessions count as the member who opened them.

SSH certificate issued means a credential was issued, not that SSH authentication or a terminal opened successfully. Failed connection attempts can leave these rows; a certificate can also be reused, so the rows are not a count of successful sessions.

What is recorded

Server-observed kinds record names and hosts, never values, contents, keys or tokens:

Client-reported kinds never record stdout, stderr, file contents, the prompt beyond its first line, or a VNC password:

From the CLI and the API

prized team log                                   # the last 24 hours
prized team log --since 7d --kind exec,prompt --member ana@acme.com

Columns and flags are on CLI: Team. GET /api/v1/audit takes the same filters and pages by before and limit; format=csv streams up to 50,000 rows (API reference).

Scheduled export

Owners set a URL and a write-only secret in the Export section of the Audit page; its status line shows the last delivery and the last error. The copy is yours, at your endpoint; there is no hosted destination.

openssl dgst -sha256 -hmac "$SECRET" body.json   # must equal the X-Prized-Signature hex

Retention

Rows are kept 90 days by default, or 7 to 365 as the owner sets under Policies. A row outlives the API key, member and box it names, and goes when the workspace is erased (Data retention). Zero data retention does not shorten the window, but with it on the exec, file.upload, file.download and prompt rows keep no detail (shown as no detail kept (zero data retention)).

Scoped secrets

A secret is workspace-wide until you grant it to a box or a member.

A secret created with an Available to choice (or grants on the API) starts with those grants; a connector's secret starts granted to the box you connected it to. A box whose grant is revoked loses the value within 15 seconds, and its mount shows no longer granted until you unmount it.

Grant from the dashboard (Available to on the new-secret form, Details on a row), the CLI (prized secrets grant NAME --box BOX or --member EMAIL; CLI: Secrets), or the API (POST /api/v1/secrets/{id}/grants; API reference). Mounting a secret the box may not have is 403 secret_not_granted.

Usage

A use is one HTTPS request to an allowlisted host in which the broker swapped in the value, counted whatever the upstream answered; refused plain-HTTP requests, other hosts, and requests without the placeholder do not count. Recorded: the placeholder, the host, the count, and the first and last time; never a path, header, body or value. Counts are a floor (a box restart can lose the last batch); read them under Details on the Secrets page, with prized secrets usage NAME, or from GET /api/v1/secrets/{id}/usage.

Team activity

Dashboard → Activity (Dashboard: Activity) shows what the team is doing now; contractors see their own boxes only.

prized team status prints the same, and --json the object GET /api/v1/team/status answers (CLI: Team, API reference).

What is not covered

• What happens inside an ssh session. SSH certificate issuance is recorded (box.connect), not whether the connection succeeded or the commands typed in it.
• Keys that belong to nobody. An API key from before workspaces existed is bound by no per-member policy, and its rows name no member (API keys).