# Members

## What is a workspace?

A workspace holds your dashboards, chats, notebooks and skills, and the people who work on them are
its members. Vistazo creates a personal workspace for you the first time you sign in. A shared
workspace is one you create for a team, and you run it from **Settings → Members**.

## How do you create a workspace?

You can create up to five workspaces, your personal one included, and join as many as you are invited
to. Each membership carries its own allowances, so joining a team workspace takes nothing from your
personal one. Leaving a workspace leaves your other workspaces as they were.

Creating a shared workspace takes two steps. The first asks for a **Name** and a **Slug**, the short
name in the workspace's web address. The second is where you add the people to invite.

## How do you invite people?

An admin invites people by email from **Settings → Members**. Changes to the roster are staged first.
**Review** lists them, and **Apply** sends the invitations.

The email's button opens a page naming the workspace and who invited them, with **Accept invitation**
and **No thanks**. They sign in with the address the invitation went to, and accepting takes them into
the workspace. The email is the only way in, because Vistazo shows no list or banner of pending
invitations. An invitation expires after 7 days.

Invitations cost nothing, and everyone you invite can build. A shared workspace holds up to 10 people,
and pending invitations count toward the ten. The roster's footer keeps the count, such as "7 of 10
people". At ten, another invitation is refused with "Workspace is full at 10 people", until you revoke
an invitation or remove a member. Some workspaces are set up without this limit, and their footer
reads "7 of ∞ people" instead.

An invitation from **Settings → Members** makes someone a member of the workspace. Sharing one
dashboard, chat, notebook or skill by email with someone outside the workspace is a different
invitation, which makes them a guest who can read only what was shared
([How sharing works](/docs/sharing/overview)).

A pending invitation's menu has **Resend invitation** and **Remove member**, which withdraws it. Daily
caps on invitations sent and on emails to one address keep a mistyped address from being mailed again
and again. The figures are on [Limits](/docs/reference/limits).

## What can each role do?

| Role | What they can do |
|---|---|
| Admin | Invites and removes people, edits workspace settings and the theme, and holds owner access to every dashboard, notebook and skill in the workspace. Chats stay private to the people they were shared with |
| Member | Builds dashboards, notebooks, chats and skills, and opens what the workspace shares with them |
| Guest | Reads only what was shared with them. Not counted toward the ten |

Everyone who is a member can build. You choose no license when you invite someone, and **Settings →
Usage** shows each member's license as **Builder**, the license that lets a person build. Each member has their own monthly inference and
compute allowances ([Usage](/docs/billing/usage)). What a member may do to one dashboard, chat or
skill is set on that object ([Permissions](/docs/sharing/permissions)).

The roster is open to every member of a shared workspace, so anyone can see who to ask for access.
Members who are not admins see it read-only, and guests do not see it. Admins also see how much of
their allowance each member has used.

## Who is a guest?

A guest is someone outside the workspace who was sent a dashboard, chat, notebook or skill by email.
They hold only what was shared with them, always read-only. It opens inside their own workspace, so
they never see yours ([How sharing works](/docs/sharing/overview)).

Admins see guests in their own **Guests** group in **Settings → Members**. A guest's menu has **Make
member**, **View artifacts** and **Remove guest**. **Remove guest** ends their access to everything that
was shared with them. A guest cannot be an admin, and giving one the admin role from your agent makes
them a member in the same step.

## What happens when an owner leaves?

A dashboard, notebook or skill stays where it is when its owner leaves the workspace or is removed, with
every grant intact. In its **Settings → Sharing** the owner's row reads **Former member** and "Left the
workspace". The list opens with "The owner has left the workspace." and a **Claim** button.

Claiming makes you the owner, and no admin is needed. The people closest to the object come first.

1. A member who co-owns it
2. People it was shared with as editors
3. People it was shared with as viewers
4. Members who can open it through its workspace row

**Claim** shows only to people in the highest group anyone currently fills. An admin can claim from any
group, or pick the new owner with **Change owner** instead. Guests cannot claim. A
chat is never claimed, because it is a private thread.

Claiming a dashboard changes three things.

- Its refresh schedule turns off, because scheduled runs use the owner's connections. Turn it back on
  from the dashboard's **Settings → General** once your own connections cover its charts.
- The departed owner's files on it move to you, with the tables read from them, and count toward your
  storage. Until someone claims, those files stay live and the charts built on them keep working.
- Public access and embeds stay as they were.

A claim is recorded in the audit log like any other change of owner.

## How do you delete a workspace?

Any admin of a shared workspace can delete it, from the **Delete workspace** row under **Settings →
General → Details**. Vistazo asks you to prove it is you, then to type the workspace's name.

The workspace closes the moment you confirm. Its dashboards, chats, skills and connections are shut to
every member, its schedules stop, and its public links stop serving. Anyone who opens it sees a notice
naming the date it will be erased, 30 days later. Any admin can cancel from that notice, and nothing is
destroyed before that date.

Every member is emailed when deletion starts and again three days before the date. Guests are not. The
email and the notice link to **Download your work**, where each member can take the dashboards, skills,
notebooks and chats they own there.

Members lose the membership and keep their accounts. Their other workspaces are untouched, and anyone
whose only workspace this was gets a personal workspace back. A workspace being moved into another
organization cannot be deleted until the move finishes, and the page says to try again in a few
minutes. A personal workspace is deleted only with its account
([Security](/docs/account/security#how-do-you-close-your-account)).

## Where are the other admin settings?

**Settings → Models** holds the workspace's own model-provider keys, which run the built-in assistant
on your provider account instead of your inference allowance. Admins manage it
([Plans](/docs/billing/plans#your-own-api-key)).

Single sign-on, directory provisioning and domain verification are not part of early access. Under
**Settings → General**, **Authentication** holds the workspace's two-factor and support access
policies.

Vistazo records administrative changes, including role changes, invitations, limit changes and changes
of owner. Settings has no view of the log. Your agent reads it with the `list_audit_log` tool
([Workspace administration](/docs/mcp-tools/administration)).