Troubleshooting & support · Resolve access and availability

How to restore paused profile access

Respond to subscription, entitlement or workspace-placement blocks.

On this page

Before you start

  • Note the exact Profile access paused or eligibility message and the selected instance/profile.

Follow these steps

Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.

  1. If you are a member, save the visible message/reference and contact an instance administrator. Do not change profile roles repeatedly or create another login to bypass the block.
    Profile access paused message in the Operations profile.View full size ↗
    If the entire profile is paused, an instance administrator must check its subscription and workspace placement before feature-specific troubleshooting.
  2. As an instance admin, open Subscription & modules and check active base access plus Process Hub entitlement if that is the affected feature. Review provider suspension/cancellation and trial/service dates.
  3. Open Admin → Fabric and check the profile workspace’s current placement. BYOF needs an activated eligible capacity; Managed needs an instance-owned Managed workspace placement.
    Fabric Capacities tab showing Active, Activated, Default, Events received and Manage stream.View full size ↗
    Check Fabric state, Emplyr access and event collection separately. This example capacity is activated and receiving events; amounts are fictional.
  4. Correct the subscription or placement through the approved administrative flow. If Fabric placement is temporarily unverifiable, restore the connection and allow validation to succeed before retrying writes.
  5. Return to the affected profile and refresh/reopen it. Web access rechecks automatically; a recovered page may refresh its context.
  6. On Android, reconnect and let eligibility validate before syncing. Keep queued answers/attachments stored; a commercial block is retryable and is not a reason to erase the app.

What you should see

Access resumes when the required entitlement and placement checks allow it. Unenrolled legacy instances do not use this commercial enforcement.

If something goes wrong

Roles/modules are correct but access is still blocked

These are independent conditions. Check entitlement and placement as well as permissions.

Changing the workspace is not appropriate

Coordinate with the workspace/process owner. Moving or rebinding business data has implications beyond this access message.

Need a hand?

Contact your organisation’s Emplyr administrator using your usual internal support channel.

How to ask for help