An organisation is xysq for a company. It groups people who share a work email domain, gives each of them a work vault that’s kept fully separate from their personal one, and lets you organise that work into teams.
If you sign up with a business email (for example you@acme.com), xysq treats you as a work account and routes you into your organisation. Personal accounts (Gmail, Outlook, and the like) stay personal and never see an organisation.
Personal and organisation memory are walled off from each other by design. Your work vault is scoped to the organisation; nothing you store there leaks into your personal vault, and nothing personal leaks into work. This separation is enforced everywhere, including in the agents you connect over MCP.
How you get an organisation
It happens during onboarding, based on your email domain:
- Business domain, organisation doesn’t exist yet - you create it. Pick a name, confirm the domain, and you become the owner.
- Business domain, organisation already exists - you can request to join. An owner or admin approves you, and you land in the organisation.
- Consumer domain - no organisation. You get a personal account.
Already onboarded and want to spin up a new organisation? Start it from your Profile.
Members and roles
Everyone in an organisation has one of three roles:
| Role | What they can do |
|---|
| Owner | Everything an admin can, plus transfer ownership and delete the organisation. |
| Admin | Invite and remove members, change member roles, edit organisation settings, manage teams. |
| Member | See the organisation’s teams and shared resources. Can’t invite or manage. |
The admin panel
Owners and admins manage the organisation at /org/:orgId/admin. It has three areas:
- Overview - the organisation’s plan and usage at a glance: seats used against your seat limit, team count, and total memories against your plan’s limit. Admins can request a plan upgrade from here.
- Members - the member list with roles, plus pending invitations. Invite by email, change a role, remove a member, or resend and revoke invitations.
- Danger - owner only. Transfer ownership or delete the organisation.
Inviting members
Invitations go to email addresses inside your organisation’s domain. An invite to an address outside the domain is rejected, which keeps the organisation scoped to your company. Invited teammates accept through a link and land directly in the organisation.
If someone with a matching domain signs up independently, xysq offers them a request-to-join flow instead of silently adding them; an admin approves the request.
Plans and seats
Each organisation runs on a plan with limits on seats, teams, team size, and total memories:
| Plan | What it means |
|---|
| Trial | A new organisation, exploring xysq. |
| Paid | An active subscription. |
| Lapsed | The subscription has expired. The organisation can still recall and browse existing memory, but new memory can’t be written until it’s renewed. |
Teams inside an organisation
Teams work the same as personal teams: a shared vault, roles (ro, rw, admin, owner), email invitations, and a recall toggle. The difference is that teams created inside an organisation belong to it, and their members come from the organisation.
Manage organisation teams from /org/:orgId/teams. Personal teams and organisation teams stay separate; you won’t see one from inside the other.
Connecting agents in an organisation
Work accounts connect their agents to an organisation-scoped memory server, not the personal one. When you open the Connect Agent guide while in your organisation, the connection URL is your organisation’s scoped endpoint:
https://api.xysq.ai/mcp/org/<your-org-id>
A work account can only use its organisation-scoped server. Pointing an agent at the bare https://api.xysq.ai/mcp URL returns an authorisation error telling you to connect to /mcp/org/<your-org-id> instead. This is what keeps work memory from ever landing in a personal vault by accident. Always copy the URL straight from the Connect Agent guide while you’re in your organisation, so it carries the right scope.
What’s personal vs what’s organisation
| Surface | Personal | Organisation |
|---|
| Vault | /vault | /org/:orgId/vault |
| Teams | /teams | /org/:orgId/teams |
| Connect Agent | personal MCP URL | organisation-scoped MCP URL |
- Teams - shared vaults, roles, and recall
- Vault - how memory is scoped and browsed
- Connect your agent - the agent setup the organisation URL plugs into
