---
title: "Guest users"
description: "A guest account has no organisation-wide access. What a guest can reach is decided by its access scope: chosen on the invitation, or See the holarchy when none was chosen."
category: administration-security
section: users-and-access
tags: [admin]
type: Reference
lastUpdated: 2026-10-26
locale: en
canonical: https://support.talkspirit.com/en/administration-security/guest-users
---

# Guest users


A **guest** is an account that gets none of the organisation-wide access a member has. What a guest can reach is decided by the **Access scope** the guest was given: chosen on the invitation, or **See the holarchy** when nobody chose one. That is why two guests in the same organisation can see very different things.

You recognise a guest by the `Guest` badge in the **Role** column of **Administration > Users**, and by **(Guest)** printed after their name in the **Members** app.

## Guest is not a rank below member

Behind the interface, an account is either a member or an administrator, and "guest" is a separate restriction carried on top of that. The **Role** column shows it as a third value, but an account can never be a guest and an administrator at the same time.

The practical consequence is that a guest cannot be promoted straight to administrator. Set them as **Member** first, then as **Administrator**. [User roles and permissions](/en/administration-security/user-roles) covers the ladder and the row menu.

## What a guest can reach

The **Access scope** on the invitation decides everything:

- **See the holarchy** gives the guest read access to the organisation's structure, every circle and every role, view only. It is the option the invitation dialog offers first, and it is also the scope a guest gets when nobody chose one: **Set as Guest** and SCIM provisioning with `userType` `Guest` both create a guest with this scope.
- **Access 1 group** and **Access more than 1 group** confine the guest to the groups you pick and nothing else.

| Where | Guest invited with **See the holarchy** | Guest confined to groups |
| --- | --- | --- |
| **Structure** | Whole structure, read only; can hold roles, never decides | Not offered |
| **Members** | Whole directory | Whole directory |
| **Groups** and **Newsfeed** | Only their own groups | Only their own groups |
| **Projects**, **Goals**, **Meetings** | Only the ones they are added to | Only the ones they are added to |
| **Home**, **Cockpit**, **Chat**, **Calendar** | Yes | Yes |
| **Library** | Only if guests are allowed in it | Only if guests are allowed in it |

So the common belief that a guest only ever sees the groups they were invited to is true of the two group scopes and wrong about the third. A guest invited with **See the holarchy** browses your whole organisation chart. If that is not what you want, invite them into groups instead.

App names can be changed for your organisation under **Administration > Terminology**, so the labels above may read differently on your screen.

### Projects, goals and meetings: only what they are added to

A guest has no organisation-wide read of **Projects**, **Goals** or **Meetings**. A public project, a public goal or a public meeting is open to every member, and stays invisible to every guest, whatever their access scope. No setting opens that tier to a guest: reading it takes a member licence.

What a guest does see is what they were added to individually: a project they were made a member of, a goal they own or are assigned to, a meeting they were invited to. They act on it with the rights that were given, so a guest added to a project as a contributor is a contributor on that project. The **Projects** and **Meetings** entries appear in a guest's navigation only once at least one is open to them.

A guest invited with **See the holarchy** can also hold a role or sit in a circle, and assigning them works as for a member. The role gives them no say in governance, as the next section explains.

### Every guest sees the whole member directory

This one surprises people, so it is worth stating plainly. The **Members** app is open to every account, guests included. A guest can browse every person in your organisation and open any profile. There is no setting that hides the directory from guests.

If someone must not see who else is in the organisation, a guest account is not the right answer.

## Can a guest who holds a role govern?

No. A guest can hold a role or sit in a circle, but is never a decision maker of that circle and never a circle admin, whatever their access scope and with or without the Holacracy add-on. A guest who holds a role:

- **Keeps the role and reads the whole structure.** Nothing about the assignment changes.
- **Never decides.** They cannot create, submit, vote on, object to or adopt a proposal, never count as a voter, and cannot add a role, a sub-circle or a working agreement. The **New** button of the **Structure** app is not shown to them. The circle's **Members** tab reads **Non-Decision Maker** on their row, with the explanation "Guests are never decision makers. Make them a member to give them a say in governance.", and the row menu has no **Set as Decision Maker** item.
- **Is never a circle admin**, whether set as admin on their row, through a role that grants circle admin, or through the circle's lead role. They cannot assign people to roles, name circle admins or decision makers, or change the circle's settings. Their row carries no **Circle Admin** badge and the row menu offers no **Upgrade to circle admin**.
- **Cannot nominate in a role election.** The election says "Guests cannot nominate in elections. A member who runs the meeting can add the nominees." A guest can still be nominated, be elected, and withdraw a nomination of their own.
- **Stays on a guest licence.** The person remains a guest and takes no member seat.

![Members tab of the Operations circle: the guest Noah Keller's row reads Non-Decision Maker and its open actions menu offers only Copy URL and Remove from circle, while the member rows above carry no such label](/images/administration-security/guest-users/02-circle-members-tab-guest-row.png)

Setting the person as **Member** restores everything at once: their assignments count as decision-maker assignments again and a circle-admin status they already held applies again.

## What no guest can do

Whatever their access scope, a guest cannot:

- **Create a project, a meeting or a goal.** Guests are excluded from creating all three. They read only the ones they are added to, never the organisation-wide public ones.
- **Open a group they do not belong to**, including open ones. A member sees every group that is not secret; a guest sees only their own.
- **Create a group.**
- **Invite anyone.** The invitation is refused even when **Allow members to invite new members** is switched on.
- **Be an administrator**, either of the organisation or of a delegated app in classic Talkspirit.

Guests can be suspended, restored and anonymised like any other account.

## How do I recognise a guest?

You need administrator rights for this route.

1. Go to **Administration**, and under **People** click **Users**.
2. Click **Filter** at the top right.
3. Under **Quick filters**, click **Guests**.

![The Users page in Talkspirit Administration with the Filter panel open, showing the Members and Guests quick filters above an Add filter control](/images/administration-security/guest-users/01-administration-users-guests-filter.png)

**Add filter** then offers a **Role** filter with the same three values, which you can combine with a status filter.

The **Members** app carries the same **Guest** quick filter, so any member can tell who is a guest without opening Administration.

## Turning a guest into a member

On a guest's row in **Administration > Users**, the actions menu offers **Set as Member**. That single step removes the restriction and gives the person full member access. It is covered step by step in [Changing a member to a guest or a guest to a member](/en/administration-security/making-a-member-a-guest-or-making-a-guest-a-member).

Two things to know before you use it in the other direction:

**Set as Guest always gives the guest the See the holarchy scope**, whatever the person had before. They can read the whole organisation chart, view only, and nothing else of what a member reaches. That includes a guest who used to be confined to groups: if you set them as **Member** and later as **Guest** again, they come back with **See the holarchy**, not with their former group scope. The group scopes are only chosen when the person is invited, and there is no control that changes an existing guest's scope afterwards.

**Making someone a guest removes their delegated administrator rights** over every app in classic Talkspirit. Setting them back to member does not return those rights, so you have to grant them again.

## Are guests free?

No, and any figure you may have read about free single-group guests belongs to the old pricing grid. Guest capacity is part of your subscription, and how many you get depends on your plan. Check your plan or ask your account manager rather than assuming a quota.

## What's next?

- [Inviting new users, members, or guests](/en/administration-security/inviting-new-users-members-or-guests)
- [Changing a member to a guest or a guest to a member](/en/administration-security/making-a-member-a-guest-or-making-a-guest-a-member)
- [User roles and permissions](/en/administration-security/user-roles)
- [Members and guests settings](/en/administration-security/members-and-guests-settings)
