Profiles per teammate
Control access with permission profiles that define object and field visibility for each member. Owners and admins configure profiles in Setup, and Pilot enforces those rules during operational searches, updates, and related workflow actions.
100%
Enforced turns
Search and write respect profiles
5min
Profile setup
Typical first role configuration
0
Shadow admins
When access is profile-scoped
Right data for every role
Profiles gate objects and fields; Pilot enforces on every turn.
Permissions in OSTRATA are profile-driven, allowing teams to define practical access boundaries by role. Instead of broad all-or-nothing rights, profiles can grant read, write, or hidden states across objects and specific fields where precision matters.
This configuration is enforced during actual usage, not only in static UI checks. Pilot evaluates the active member profile before data operations, helping teams adopt conversational workflows while maintaining control over sensitive records and fields.
Profile-based access control
Assign rights by role so each teammate gets only the object and field surface required for work.
Field-level precision
Hide sensitive attributes while still allowing operational work on the same underlying records.
Pilot enforcement in execution path
Permission checks occur before searches and updates, keeping conversational actions aligned with policy.
Profiles
Access model built for mixed team roles
Assign profile-based access so each role sees only needed data.
- Define rights once and reuse across members
- Support sales, ops, leadership, and support scopes
- Reduce overexposure during onboarding and transitions
Field scope
Object-level and field-level controls
Control access at object and field levels for precise governance.
- Grant read or edit rights by record type
- Mask sensitive values inside shared objects
- Balance collaboration with confidentiality requirements
Assignment
Operational safety for Pilot workflows
Pilot checks profile permissions before executing every conversational action.
- Constrain search and updates by active role
- Prevent unauthorized visibility in fast workflows
- Enforce policy systematically, not by prompt discipline
Audit
Administrative workflow in Setup
Admins manage profiles centrally in Setup as teams change.
- Assign profiles during invite or role changes
- Avoid rebuilding custom rules per user
- Support audits with clear governance ownership
Handoffs
Consistency across features and interfaces
Profile rules apply consistently across Operations, Views, and shared outputs.
- Prevent mismatched visibility between product surfaces
- Keep onboarding expectations clear for new members
- Build trust through predictable access behavior
Questions
Short answers before you request access.
- Who can configure permission profiles in OSTRATA?
- Workspace owners and admins manage permission profiles in Setup. They define access levels and assign profiles to members based on role responsibilities. This central ownership keeps governance coherent while allowing day-to-day users to operate without managing policy details.
- Can permissions restrict individual fields, not just objects?
- Yes. Profiles can apply field-level controls, allowing teams to hide specific sensitive attributes while still granting access to the rest of a record. This supports collaboration on shared objects without exposing confidential values to every member role.
- How are permissions enforced in Pilot chat actions?
- Pilot checks the active member profile before executing searches or updates. If a role lacks access, the action is constrained accordingly. This enforcement happens during execution, so conversational workflows remain fast without bypassing workspace governance controls.
- Do permissions help as teams scale?
- Yes. Profile-based access scales better than per-user exceptions. Teams can onboard members by assigning existing profiles, then refine roles over time. This keeps access policy manageable while preserving operational consistency across departments and changing responsibilities.