From Users, open the person — or start a new one — and choose Add as Tribe Admin. Pick the tribe, confirm their name and email, and set their permissions.
Full or restricted access
THE DEFAULT IS FULL ACCESS — EVERY PERMISSION TICKED
Both the new dialog and the older administrators screen start with Full Access selected, which grants the whole tribe permission set. Choose Restricted Access and tick only what the person needs, unless you genuinely mean to give a branch manager everything.
One group deserves particular care. Tribe Setting includes the ability to delete the tribe, and Tribe Administrators lets that person add and remove other administrators. Neither is obvious from the name.
The permission list only shows modules your organisation actually has switched on, so it is shorter than the organisation role screen.
The invitation has two acceptances
ACCEPTING THE ORGANISATION INVITE DOES NOT ACCEPT THE TRIBE ONE
Somebody invited to administer a tribe gets an invitation to join your organisation and a separate invitation for each tribe. Accepting the first does not accept the others. This is the single most common reason a new manager says they can log in but cannot see their tribe.
Both acceptances live in the notifications area inside Gorilla Dash, not in the email. The email for somebody who already has an account simply links them there. Tell new administrators to check the bell menu.
They must register with the invited address
A DIFFERENT EMAIL BREAKS THE INVITATION PERMANENTLY
If somebody is invited at one address and creates their account with another, the invitation never reaches them and cannot be recovered by resending. Remove them and invite the address they actually use.
Unaccepted invitations chase themselves
An invitation that has not been accepted is sent again automatically. Two days after the original, the person receives it a second time; two days after that, a third time if it is still pending; and then it stops. You do not need to watch the pending list or resend by hand.
Each reminder is recorded against the invitation, though that record is not shown on any screen — if you need to know exactly what went out and when, ask Gorilla Dash support. If somebody has had the invitation and both reminders and still not accepted, the problem is usually not the email: check the address is right, and that the invitation is not sitting in a shared mailbox nobody reads.
When Resend does nothing
For somebody who already has a verified Gorilla Dash account, Resend does not send an email — it re-links their in-app notification and reports success. They will find the invitation waiting in their notifications. Point them there rather than resending repeatedly.
Team member at the same time
The dialog offers Create Team Member, on by default, which also puts them in the Organisation Chart for that tribe. Leave it on — it is what makes them appear in contact lists, the tribe directory and your website team page. Team Member access alone will not grant access to the tribe’s application and will result in a 403 for that area.
Troubleshooting: 403 "Access denied" after accepting an invite
If a user can sign in to Gorilla Dash but cannot see your company/tribe and receives a 403 "Access denied" message, they were likely invited only as a Team Member, not as a Tribe (location) Administrator.
To fix:
- Have an existing administrator open the tribe's Administrators page (not the Team Members menu).
- Invite the user as a Tribe Administrator and assign the appropriate permissions.
- Ask the user to accept the new administrator invitation and sign in again.
Only Tribe Administrators with the correct permissions can access the tribe's application. Team Member access alone will result in a 403 for that area.