Chart Basics
What the Organisation Chart is for
A staff directory, a reporting structure, and the contact lists that four other parts of Gorilla Dash send to.
Last updated September 2, 2026
The Organisation Chart does three jobs at once, and it is worth knowing all three because most people only discover the third by accident.
- A staff directory — every team member, advisor and vendor contact in your network.
- A reporting structure — departments, positions and who reports to whom, drawn as a chart.
- The contact-list engine — the source of truth for who gets invited, emailed and texted internally.
Three different kinds of "person"
| Record | What it is | Where it lives |
|---|---|---|
| Team member | A member of staff. Exists whether or not they can sign in. | Organisation Chart → People |
| User | A login account. | Users and permissions |
| Contact | A customer or lead. | People and CRM |
A team member is linked to a login where the email matches somebody who already has access. Shared mailboxes like info@ attached to several records are deliberately not auto-linked — those need inviting by hand.
What else depends on it
Contact lists built here are what the following send to. If a list is wrong, all of them are wrong:
- Event Calendar invitations.
- Internal Emails and Internal SMS.
- Weekly Digest recipients.
- Vendor mailing lists.
Organisation Chart roles are also what the Resource Library and Knowledge Base use when you restrict something to specific roles.
Everything here is organisation-level
The chart, the people and the lists belong to the organisation. Tribes get a read-only Who to Call contact board and nothing else.