Teams and access
Projects, roles, invitations, and the difference between personal account and team workspace in MASAIC.
MASAIC separates your personal account from team projects (workspaces). Agent configuration, prompts, MCP servers, and automation almost always live on the team side.
Personal account vs team project
| Personal account | Team project (workspace) | |
|---|---|---|
| URL pattern | /home/... | /workspace/<slug>/... |
| Typical use | Profile, billing, seeing which teams you belong to | Building and running agents |
| Data scope | Your user | Shared team assets |
You still sign in once; the switcher moves between personal and team contexts — in a workspace at the start of the path above the page, on your personal home at the top of the sidebar.
Roles
Project rows on Home show a Role (for example owner or member). Exact permissions depend on your plan and how your admin configured the product, but generally:
- Owners can manage membership, billing (where applicable), and critical settings.
- Members can usually edit agents and content their policy allows.
Ask an owner to invite you if you cannot see the right project.
Invitations
Invites are sent to your email. Accept from the link, then sign in with the same address. If you use Google or SSO, match the identity your admin invited.
Security habits
- Use least privilege—grant only the roles people need to change production agents.
- Prefer staging environments for experiments (testing and release).
- Treat MCP servers like production services: approval, ownership, and monitoring (MCP).