Permissions

Permissions decide what a team member can see and do inside your tribe. Every area of the dashboard is its own row, and each row is set to one of three levels, so you can be as broad or as surgical as you like.

This page covers the levels, the capabilities that sit outside them, the full list of areas, and the role presets that fill it all in for you.

The three access levels

For every area, a member has exactly one of:

• All Access: view everything in the area and make changes. Create, edit, delete, send, publish, refund, and so on.
• Read Only: view everything in the area, with none of the buttons that change anything.
• No Access: the area is hidden. The link doesn't appear in their sidebar and they can't open it directly.

All Access always includes viewing. There's no state where someone can edit something they can't see.

Capabilities that are not levels

Two things in the editor are checkboxes rather than dropdowns, because they are single jobs rather than a level of access. They sit indented under the area they relate to, and they work on their own:

• Door check-in, under Events. The person can scan tickets and read the door list for your events, and nothing else. Granting it does not open the Events area, and setting Events to All Access does not grant it.
• Approve timesheets, under Time Tracking. The person can approve other members' hours for payout. Logging your own hours is Time Tracking All Access. Approving someone else's is deliberately not the same thing.

Tick or untick these independently of the dropdown above them. Nothing about the dropdown changes them, and nothing about them changes the dropdown.

The areas you can grant

The Edit Permissions dialog lists every area in one column, in the order below. Each row gets its own dropdown set to All Access, Read Only or No Access.

Not everything is on this list. Access to a knowledge base space or document is granted on the space or the document itself rather than here, so you won't find a row for it.

The money areas are owner-only

Finance and Invoices can only be granted by the workspace owner. If you're an admin editing someone's permissions, those two rows don't appear for you at all, so you can't grant what the system would refuse.

The owner grants them from the same dialogs everyone else uses. See "Adding financial access to an admin" below.

Role presets

Setting thirty rows by hand gets old fast, so the invite dialog and the edit dialog both open with a Role Preset dropdown. Pick one and the rows are filled in for you. You can still change any individual row afterwards.

Built-in presets

• Admin: everything except the financial areas. This one is special, see below.
• Content Manager: memberships and posts, blog, emails, courses, coaching, events, streaming, collections and the website.
• Store Manager: products, coupons, offers, donations, invoices, memberships and the website.
• Marketing: emails, smart links, forms, coupons and the website.
• Event Manager: events, streaming, emails and the website.
• Door Staff: the door check-in capability and nothing else. See below.
• Read Only: view-only across everything except the financial areas. Good for a stakeholder or an accountant who needs visibility without edit rights.

Any custom roles saved for your workspace appear in the same dropdown, under the built-in ones. Custom at the bottom means "I'm setting these by hand".

Admin is a live role, not a snapshot

Choosing Admin doesn't copy a list of permissions onto that person. It marks them as an admin, and the dashboard resolves what that means every time they use it.

The practical effect: an admin automatically gets new areas as TribeNest adds them, without you going back to re-grant anything. The dialog says as much on screen, under the preset dropdown.

Adding financial access to an admin

An admin has everything except Finance and Invoices. If you're the owner and you want one of them to have those too:

1. Open the invite dialog, or the pencil on a member's row.
2. Leave the Role Preset on Admin.
3. Click Grant financial access… under the preset.
4. Set Finance and Invoices to the level you want, then click Done.
5. Send the invite, or click Save Permissions.

Only the owner sees that link. An admin managing the team never does.

The door-only team member

Door Staff is worth calling out because it's the narrowest role there is, and the most useful one to get right.

A door-only member holds one capability: scan tickets and read the door list. They can't open your events, see who bought what, email your attendees or cancel a show. When they sign in they see the Events group in the sidebar with a single item, Door, and that item lists the shows happening around now that they can scan into. Everything else is closed to them.

That is exactly what you want for someone hired for one night. Before this existed, handing a steward a scanner meant granting the whole Events area, which also lets them cancel the show and mail the attendee list.

See the door and box office for what the door screen actually does.

Setting permissions by hand

From the invite dialog or a member's edit dialog:

1. Pick the closest Role Preset, or pick Custom.
2. Click the pencil beside Permissions to open Edit Permissions.
3. Set any row to All Access, Read Only or No Access.
4. Tick a capability checkbox if the job needs one.
5. Click Done to close the dialog.
6. Click Send Invite, or Save Permissions for an existing member.

The moment you deviate from a preset, the Role Preset dropdown switches to Custom, so you can tell at a glance that you've moved off the template.

The line under Permissions summarizes what you've set, for example "5 all access · 3 read only · 1 special access · 4 restricted". Use it as a sanity check before you save. A capability is counted separately there, never folded into the other numbers, which is why a door-only member never reads as "No access".

How to scope a member's access

A few patterns that work well in practice.

Start narrow, widen as needed

Pick the smallest preset that covers most of the job, then add one row. Your store manager needs to send a "back in stock" email now and then, so start with Store Manager and flip Emails to All Access. Everything else stays closed.

Mix read and write

Not every row is all or nothing. A bookkeeper might want All Access to Finance and Invoices and Read Only on everything else, so they can answer questions without changing anything.

Give the social manager their own area

Social Media is its own row now, covering connected accounts, posts, the calendar, analytics, the inbox, comments and automations. Someone running your social presence needs that row and very little else, so grant it on its own rather than reaching for a broad preset.

Grant Team carefully

Anyone with Team on All Access can invite, edit and remove other members, including changing your permissions. Most collaborators don't need that. Leave it on No Access unless you're explicitly delegating team management.

Keep Settings tight

Settings covers your workspace name, what kind of business it is, the language it writes in, and the optional features. Mistakes there are annoying to undo. If someone doesn't need to change those, leave Settings on No Access or Read Only. See settings.

Where to go next

• Send an invite with the right preset → inviting team members
• Edit an existing member's access → managing your team
• Adjust the rest of your workspace setup → settings