Workspaces and team
Every run, sync key and membership on https://app.agenticml.xyz belongs to one workspace. A workspace has its own address, https://app.agenticml.xyz/w/<slug>/. If you belong to more than one, the workspace switcher is under Settings > Account. Every page’s top bar has a Workspaces link back to your workspace list and Sign out.
The server treats a workspace you do not belong to as if it did not exist: it answers “not found” to a key, a session or an address from another workspace. A live check of this on the hosted service is still on the open list.
Each person has one role in each workspace.
| Role | What it can do |
|---|---|
owner |
Everything an admin can do. The creator of the workspace. Cannot be removed. |
admin |
Invite and remove people, change roles, and make or revoke sync keys for anyone in the workspace. |
member |
Read the dashboard, sync runs, and make or revoke their own sync keys. |
viewer |
Read the dashboard. A viewer’s key can only call agenticml whoami; it cannot sync. |
Invite someone
Section titled “Invite someone”Owners and admins use Settings > Members.
- Open Settings in the top bar, then Members.
- Enter the person’s email in Login or email.
- Pick a role:
viewer,member(the default) oradmin. - Click Send invite, copy the link, and send it to them.
The link works once and expires after 72 hours. The person opens it and signs in with Google, or with email and password, using the same email you invited. The email must be verified. Pending invites are listed under Pending invites in the same card, where you can revoke them.
If the email already has an account on the hosted service, the person is added to the workspace straight away and no link is made.
To remove someone or change their role, use Remove or the role menu in the Members list.
People limit
Section titled “People limit”A free workspace has up to 5 people. Members and pending invites both count. When the limit is reached, inviting someone else fails with HTTP 403 and people limit reached (5 of 5). Revoke an invite or remove a person to make room. The Usage section under Settings > Workspace shows how many of the 5 are used.
Settings page
Section titled “Settings page”Open Settings in the top bar. What you see depends on your role.
- Account: your user, role and sign-in method, the workspace switcher, and sign out. Servers without Firebase sign-in also show a password form.
- Workspace: name, slug, plan and Usage (storage, daily uploads, requests per minute and people against the free plan limits). Owners and admins only.
- Members: people, roles, invites and pending invites. Owners and admins only.
- API keys: your sync keys, with a New key button. Owners and admins also see the keys of other people and can make one for a person with the User field. A key is shown once, when it is made.
- Activity: recent audit events. Owners and admins only.
- Usage banner: a banner at the top of the dashboard appears when storage or daily uploads pass 80% of the limit, and again when the limit is reached.
Viewers see only Account. Members see Account and API keys. The switcher appears only if you belong to more than one workspace, open sign-up is on, or you are a server admin.
Only the operator can delete a workspace. Send deletion requests to contact@agenticml.xyz, as the Privacy policy describes. The operator confirms privately which workspace is yours before deleting anything. Do not post your workspace slug, email or run data in a public GitHub issue.
Several workspaces from one machine
Section titled “Several workspaces from one machine”All hosted workspaces share one address, https://app.agenticml.xyz. The client saves only one key per server address, so logging in for a second workspace replaces the first saved key. Provide the key using AGENTICML_API_KEY per shell or per command from your secret store.
Sync progress is tracked per server and workspace (<host>/w/<slug>). A single local store can sync the same run to multiple workspaces on the host without conflict. Sync each workspace with its own key:
export AGENTICML_HOST=https://app.agenticml.xyz
# Train once in the local storeagenticml run train.py
# Sync to workspace AAGENTICML_API_KEY="$TEAM_A_KEY" agenticml sync --all
# Sync to workspace BAGENTICML_API_KEY="$TEAM_B_KEY" agenticml sync --allTo clear saved progress for a run, agenticml sync RUN_ID --reset forgets every cursor for this host across all workspaces. The next sync asks the server what it already has and uploads the rest.
Older clients keep one cursor per server address. If a run you synced to one workspace reports “up to date” when you sync it with another workspace’s key, install the client again from dev, or run agenticml sync RUN_ID --reset before syncing with the second key.
The first sync after you upgrade checks each run you synced before, once: one short request per run, and nothing is uploaded twice.