Chapter 09
Team and permissions
Invite your brigade, manage seats, and control global or resource-specific access.
Team access is designed for a kitchen or business that needs shared work without making every resource public to every member.
Owner responsibilities
The owner manages:
- team name and logo;
- invitations and reusable invite links;
- members and pending invitations;
- plan and purchased seats;
- global and individual resource permissions;
- team billing and referrals.
Invite a person
Use an email invitation for a named person or a reusable link when appropriate. A pending invitation can reserve capacity, so revoke links/invitations you no longer intend to use.
If acceptance says there are no seats available, the owner must remove/revoke an existing seat use or purchase another Brigade seat.
Permission levels
Global permission grants broad access to a resource type. Individual permission means the owner selects specific projects, menus, or recipes for that member.
Use least privilege:
- give edit access only when the person should change operational data;
- prefer read access for review or training;
- review individual resource grants when a project ends;
- remember that shopping-list sharing is separate from a copied URL.
Removing access
Removing a member ends their team access but does not delete the team's resources. Revoking an invite prevents future acceptance but does not change previously accepted membership.
Before lowering Brigade seat count, remove members or revoke pending invitations until occupancy fits the new total.
Team logo and PDF
On Brigade, the team logo can replace Heard Chef branding in eligible PDF exports. Use a clear logo with enough contrast and review an export after changing it.