Profiles, people & access · Profiles and modules
Understanding profiles and modules
Understand what profile switches enable and what permissions still control.
On this page
Before you start
- Know the instance and client/department profile you are working in.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Select a profile in Context. That profile scopes its member roles, report configuration, process records and branding overrides.
- Check which modules the instance admin has enabled for the profile. The supported profile switches are Reporting, Whitelabeling, Fabric Access and Process Hub.

Enable the modules the profile needs. Members still require the appropriate role and resource access. - Ask for the role permissions needed for your task. Enabling a module exposes a capability; it does not automatically let every member view, edit or manage it.
- For a report or process, check resource-specific access too. A process must have a successful deployment before members can run its current runtime version.
- If the instance is commercially enrolled, its subscription/module entitlement and workspace placement also need to allow the profile.
What you should see
You can distinguish a profile/module configuration issue from missing personal or resource access.
If something goes wrong
There is no Users or Settings module switch
This is expected. Users and Settings use role-feature permissions rather than profile activation switches.
Profiles share a workspace
This is supported. The workspace binding alone does not grant another profile’s Emplyr access or guarantee isolation within Fabric.