Invite your team
A project can have many people. Each person signs in with their own account and sees the same spend, requests, routing and memory.
Add a colleague
You must be an owner of the project.
- In the console, open Team.
- In Add a colleague, type the email address of the person in Their email address.
- In Role, select Member or Owner.
- Select Add.
Proxium sends no email. Tell the person to sign in at proxium.tech/app with that email address.
The person shows in People with the status not signed in yet. After their first sign-in, the status is active, and the project shows in their console.
What each role can do
| Action | Member | Owner |
|---|---|---|
| See spend, requests, routing and memory | Yes | Yes |
| Change the routing and its drawing | No | Yes |
| Change the ceilings, the vendors and the endpoints | No | Yes |
| Add a provider key to a vendor | No | Yes |
| Mint a key, and revoke the key that the member minted | Yes | Yes |
| Revoke a key that an owner minted | No | Yes |
| Save a memory, a diary entry and a goal | Yes | Yes |
| Change the stored prompts and answers, and protect the data | No | Yes |
| Export the project, without the stored prompts and answers | Yes | Yes |
| Export the stored prompts and answers | No | Yes |
| Add and remove people | No | Yes |
| Erase one end user in the console | No | Yes |
| Erase the project | No | Yes |
The console shows the controls of an owner action to a member as disabled, with the line Only an owner can change this. The gateway answers the same request from a member with the message only an owner of <project> may change this project; your role is member, and an MCP tool that writes answers the same message.
A member keeps the tools of their own work. They save memory, goals and diary entries. They mint a key, and they revoke that key.
Limit the MCP tools of a member
On the row of a member, an owner can select Tools. Type the MCP tools that the member may call, for example github__* or docs__search. Leave the field empty for every tool. An owner always calls every tool. See Connect MCP servers.
Remove a person
- Open Team.
- On the row of the person, select Remove, and confirm.
The person loses access to the project at once. For a person with the status not signed in yet, the confirm text says Withdraw the invitation.
A project always keeps one owner. The console shows no Remove on the last owner.
Related pages
- Data handling: what an export holds, and what an erasure deletes.
- Use project memory: erase one end user.