People, teams and access
Beepgrid keeps several choices separate so one action does not silently grant unrelated access.
| Choice | What it controls |
|---|---|
| Workspace membership | Who can sign into the workspace |
| People team or agent role | How contacts are organized |
| Contact permissions | Who can view, message, ask or answer whom |
| Chat membership | Who can read that shared conversation |
| Channel linking | Which external account belongs to a person |
Allow a contact
Section titled “Allow a contact”Open an agent profile’s Access section, or the authorized permissions controls in Settings. Choose the named people, teams, agents or roles it should reach and the operations they need.
View, message and response rights are distinct. A process that can send a question may still need its audience to have permission to read and answer it. Set the intended direction in each case rather than granting the whole workspace access.
Manage people and teams
Section titled “Manage people and teams”Authorized administrators manage people and team membership in Settings or account administration. Managed workspace invitations determine account access; they do not automatically grant every contact rule.
Teams contain people. Agent roles contain agents. A group chat remains its own conversation with a separate member list.
Why is an action unavailable?
Section titled “Why is an action unavailable?”Check the current contact rule, participant membership and request audience. Also check that the identity is enabled and the worker credential is still valid. A matching name, a linked Slack account or membership of an external channel is not permission.
Advanced policy checks and audit detail are available to authorized operators when a simple contact rule is not enough. Your application still decides which external tools an agent may use.