This guide explains how access and permissions work inside your Silent Push organization. It covers how the organization is structured and how Role-Based Access Control (RBAC) determines what people can see and do.
This guide is intended for Owners, Managers, and Members of a customer organization.
What is Role-Based Access Control (RBAC)?
Role-Based Access Control (RBAC) manages who can see and do what inside an application by assigning people to roles, rather than configuring permissions for each individual one at a time. Each role carries a defined set of capabilities, and every user in your organization is assigned exactly one role.
In the Silent Push platform, RBAC is built around three connected concepts:
Organization — the top-level account that contains everything: your users, teams, data, and subscription.
Team — a group of users inside your organization who share permissions built based on user persona or job titles.
Role — the level of authority a user holds, which determines what they can manage (Owner, Manager, or Member).
Together, these three concepts let you control access at the right level of granularity: broad organization-wide control for Owners, team-level control for Managers, and individual access for Members.
The structure of your organization
Organization
The Organization is the foundation of your account. Everything else, users, teams, saved queries, monitors, assets, and billing, lives inside it. Your organization's data is completely isolated from every other customer's organization.
Team
A Team is a virtual container inside your organization that groups users together, typically by persona or function. Teams exist to make management and sharing easier: instead of sharing an entity with 50 individual users, you share it once with a team. A Manager oversees the team.
User
A User is an individual person with a profile, email address, and login credentials. An Owner adds every user to the organization and assigns one of the three system roles, which dictates how much control they have.
Notes
By default, a user can belong to only one team. A Manager does not need to be on the team, but it is recommended.