TribeNest Help Center
Team

Permissions

Every section a team member can be granted, what each access level means, and how to scope a member's access to fit the job.

Permissions are how you decide what a team member can see and do inside your tribe. Every section of the dashboard is its own permission, and each one can be set to one of three access levels — so you can be as broad or as surgical as you want.

This page covers the access levels, the full list of sections, and how to use the Role Preset dropdown to move fast.

The three access levels

For every section of TribeNest, a member has exactly one of:

  • All Access — view everything in the section and make changes (create, edit, delete, send, publish, refund, and so on).
  • Read Only — view everything in the section, but no buttons that change anything.
  • No Access — the section is hidden entirely. The link doesn't appear in their sidebar and they can't open it directly.

When you grant All Access for a section, Read Only is included automatically — there's no scenario where someone can edit but not view.

Hidden, not just disabled

No Access doesn't mean a greyed-out menu item — it means the section disappears from the member's sidebar entirely. If you remove access while they're using it, they'll lose the page on their next navigation.

The sections you can grant

Each section below is one row in the Edit Permissions dialog. Set each one to All Access, Read Only, or No Access.

Content and audience

  • Websites — your tribe's public website, page builder, themes, navigation, and domain settings.
  • Blog — blog posts and categories.
  • Memberships & Posts — membership tiers, member-only posts, and the content fans get when they subscribe.
  • Smart Links — landing pages for releases and links you share off-platform.
  • Forms — contact and signup forms you embed on your site.
  • Contacts — your contact list, segments, tags, and history. (This section only appears for tribes with the contacts surface enabled.)

Commerce

  • Products — your store catalog, including merch, music, digital downloads, variants, and shipping settings.
  • Coupons — discount codes you can hand out for products or memberships.
  • Offers — promotions you build and attach to checkout flows.
  • Invoices — order invoices and customer billing records.
  • Income & Transactions — your earnings dashboard, payouts, and the full transaction log.

Outreach

  • Emails — your email campaigns, templates, automations, and audience.
  • Ads — your advertising campaigns. (This section only appears for tribes with the ads surface enabled.)

Live and learning

  • Events — concerts, meet-and-greets, and any other event you list.
  • Streaming — your live broadcast settings and stream history.
  • Scheduling — one-on-one coaching slots, availability, and bookings.
  • Courses — on-demand course catalog, lessons, and student progress.

Operations

  • Team — the Team page itself. With All Access, this member can invite, edit, and remove other team members.
  • Settings — your tribe's settings page (profile details, integrations, business info, and so on). See settings.
  • Mira (AI agent) — Mira, your built-in copilot. With All Access, the member can chat with Mira and act on her proposals; with Read Only, they can see her briefings but can't approve writes. (This section only appears for tribes with Mira enabled.)

Your sidebar may not show every row

A few sections are gated behind features your tribe may not have turned on — Ads, Contacts, and Mira are the most common. You'll only see the rows that apply to you.

Role presets

Building permissions section-by-section gets old fast, so the invite and edit dialogs both start with a Role Preset dropdown. Pick one and the right boxes get checked for you. You can still tweak any individual section afterwards.

Built-in presets

  • Admin — broad access across the dashboard. The fastest way to onboard a trusted collaborator who'll touch most things.
  • Content Manager — focused on the surfaces your fans see — websites, blog, memberships, posts, smart links, forms.
  • Store Manager — focused on running your shop — products, coupons, offers, invoices, and the income side of orders.
  • Marketing — focused on outreach — emails, smart links, ads, forms, and the audience tools that feed them.
  • Event Manager — focused on shows and learning — events, streaming, scheduling, courses.
  • Read Only — view-only across the dashboard. Good for stakeholders, accountants, or anyone who needs visibility without edit rights.

Customizing a preset

Pick a preset, then click the pencil icon next to Permissions to open the Edit Permissions dialog. Each section gets its own dropdown — flip any of them to All Access, Read Only, or No Access. The moment you deviate, the Role Preset dropdown switches to Custom so you can tell at a glance that you've moved off the template.

When you're done, click Done to close the dialog. Your changes only take effect once you click Send Invite (in the invite flow) or Save Permissions (when editing an existing member).

The line under Permissions summarizes what you've set — for example, "5 all access · 3 read only · 4 restricted". Use it as a sanity check before you save.

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 member's job, then add a single extra section if you need to. Example — your store manager needs to send a "back in stock" email once in a while, so you start with Store Manager and flip Emails to All Access. Everything else stays restricted.

Mix read and write

Not every section is binary. A bookkeeper might need All Access to Income & Transactions and Invoices, but only Read Only on everything else so they can answer questions without changing anything. Read Only is a great middle ground for stakeholders.

Grant Team carefully

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

Keep Settings owner-only when possible

Settings controls things like your tribe's name, web address, business info, and integrations. Many small mistakes here are hard to undo. If a team member doesn't need to change those, leave Settings on No Access or Read Only.

Permissions update immediately

When you save a change in Edit Permissions, the new access takes effect right away — no logout needed. If a member is mid-task when you remove access, they'll bounce on their next click. Tell them before you lock something down if it's mid-flow.

Where to go next