The main scope ideas
The exact options shown depend on the product area and the user’s permissions.
Example: two salespeople and one manager
Salesperson A owns ten open Deals. Salesperson B owns twelve. The manager has team-level visibility. Under Mine, Salesperson A should not suddenly see Salesperson B’s Deals simply because both people belong to Sales. Under team scope, the manager can review the team’s twenty-two Deals where the access model allows it. The owner may have wider workspace visibility without becoming the owner of all twenty-two records. This is why ownership and scope are separate concepts.view_all expands visibility, not authority
Permissions such as lead.view_all and deal.view_all can widen which records a user can see.
They do not automatically grant permission to create, edit, delete, assign, close, or reopen those records.
A manager may legitimately see a Deal they are not allowed to perform a sensitive lifecycle action on.
A requested scope can be reduced
A filter or report can request a broad scope, but the access layer must still enforce what the user is allowed to see. A restricted user should not become a workspace-wide viewer just because the front end sentworkspace in a query.
Scope affects dashboards and Reports
Two people can open the same report title and see different totals because their record scope differs. Before calling the calculation wrong, compare:- report period
- selected scope
- team or user filter
- product-area access
view_allor team visibility permissions- reporting exclusions
- currency and timezone when the metric depends on them
Scope does not bypass product access
Workspace-wide Sales visibility does not grant Reports access. Team-level Deal visibility does not grant Accounting. A user still needs the product area and action permissions required for the task. Think of the access chain as: workspace state → plan capability → enabled product area → role or user access → record scope → action permission → record lifecycle ruleTeams and one person in multiple groups
A user can belong to more than one team. That makes small-business structures easier to model when someone helps both Sales and Support, or when a manager oversees more than one group. Do not assume multi-team membership means the person should see every record in every product area. Product access and permission rules still apply.When a record is missing
If the user can open the area but one record is missing, investigate ownership, team membership, scope, andview_all or team permissions.
If the entire area is missing, investigate plan, installed areas, and user product access instead.
Assign work
Understand ownership without using it as a security setting.
Manager visibility
Give managers team visibility without making them Admin.