Skip to content
Remove an applet from a role

How do I remove an applet from a role? Take an applet, or part of it, away from users

“How do I remove an applet from a role?” There are two answers, and they do different things. Uninstalling an applet for a person takes it off their applet list. Removing the role’s grants takes away what everyone holding that role is allowed to do in it. Decide which you need first; it takes about ten minutes, plus a test with one ordinary user.

This page is for the tenant owner or administrator who looks after users and roles in Tenant Admin.

Meet GadgetSphere

At GadgetSphere’s GS-PEN-01 branch, cashiers hold a role called Cashier. Last year someone gave that role access to the Purchase Invoice applet so a cashier could cover a supervisor’s leave. That cover has ended, and cashiers should no longer open purchase invoices.

Before you start

  • You can open Tenant Admin and edit users and roles.
  • Know which you want. (A) One person should stop seeing the applet on their list. (B) Everyone holding the role should lose permissions in the applet. For the GadgetSphere cashiers it is (B).
  • Have an ordinary test user who holds the role and nothing more. A login that holds the tenant-wide owner or admin permission (TNT_TENANT_OWNER, TNT_TENANT_ADMIN) passes every permission check, so testing with your own login proves nothing.

Step 1 (A): Uninstall the applet for one person

Tenant Admin → Tenant Users → the person → Installed Applet

Select the applet’s row and press UNINSTALL. The applet leaves that person’s applet list.

Uninstalling removes the install, not the permissions. If the person still holds a role that grants the applet’s permissions, those grants are untouched. Use (B) for that.

Step 2 (B): Untick the role’s client-side permissions for the applet

Tenant Admin → Tenant Roles → the role → Applet → the applet → Client-Side Permissions

The grid lists the applet’s client-side permissions by Permission Code and Description — mostly what the screen shows the person: menus, buttons, tabs. Untick the ones the role should lose and press Update Permissions. Unticking does revoke them.

Step 3 (B): Remove the role’s permission set for the applet

Tenant Admin → Tenant Roles → the role → Permission Set

The Permission Set tab lists the permission sets attached to the role. Select the set that grants the applet and press REMOVE. There is no confirmation: the set is detached from the role straight away.

REMOVE takes the whole set off the role — every permission in it, not only this applet’s. Look at what the set contains before you remove it. If it also grants something the role still needs, ask BigLedger support how best to split it before you remove anything.

Unticking every branch, company or location does not do this. Under Applet → the applet → Permission Sets the Branch, Company and Location grids narrow which places a set covers. A grid with nothing ticked is skipped, so unticking all of them revokes nothing. Use REMOVE on the Permission Set tab.

Step 4: Test with your ordinary test user

Have the test user close and reopen the applet (or sign out and in), then try what they should no longer be able to do. An applet that was already open keeps what it read when it opened, so judging from an open screen will fool you.

What success looks like

Your test user — holding the role and nothing else — reopens the applet and finds it gone from their list (A), or finds the menus and actions you removed gone or refused (B). For the GadgetSphere cashiers: a cashier signs in fresh and can no longer open purchase invoices.

Common mistakes

  • Judging the result from a screen that was already open. Close and reopen first.
  • Uninstalling and believing the permissions are gone. Uninstall removes the install, not the grants.
  • Unticking every branch target and expecting access to disappear. It revokes nothing; remove the permission set instead.
  • Removing a permission set that also grants something else. REMOVE takes the whole set. Check its contents first.
  • Forgetting the person’s other roles. If access remains, open Tenant Users → the person → Roles: another role, a team they belong to, or a grant made to the person directly may still give it.
  • Testing with an owner or administrator login. The tenant-wide owner and admin permissions pass every check a role would refuse. Test with an ordinary user.

If it still does not work

Contact BigLedger support with the applet’s name, the role’s name, the test user’s sign-in e-mail, which of (A) or (B) you did, and what the user can still see or do. Crop out other people’s data from screenshots.

Related documentation

Last updated on