Revoke access

Revoke access when someone leaves a team, a program ends, or a lens is no longer relevant to a stakeholder. Removing a grant is instant for direct user grants; group and role grants take up to 15 minutes to propagate because Foundation caches Jira group membership for that long.

You need Control on the lens to revoke access.

Remove a user, group, or role

Open the lens and click Share in the toolbar.
In the Share dialog, find the grant in the permissions list.
Click the Remove button (trash icon) next to that grant.
Confirm the removal in the prompt.

The grant disappears from the list. That user loses access the next time they reload the lens.

What removal does and doesn’t do

The removed grantee loses their ability to open the lens.
Any Jira issues they still have BROWSE permission for remain in Jira untouched — revoking Foundation access is not a Jira access change.
If the user had Control and you accidentally remove themselves, Foundation still preserves ownership (owners always have implicit Control).
Removal is auditable: admins can review recent permission changes from the admin dashboard.

When changes take effect

User grants — next page load for that user.
Group grants — up to 15 minutes, because group membership is cached. Users can reload twice to bust the cache if they need the change sooner.
Role grants — same 15-minute cache window.

Handling ownership

You can’t revoke the owner’s access — ownership is implicit. To move Control to a different person:

Open the Share dialog.
Click Transfer ownership, pick the new owner, and confirm.
Once they become owner, you can revoke your own additional grant if you want to step away entirely.

If someone still has access after revoking

Confirm they’re reloading the lens, not looking at a stale tab.
Check if they belong to a group that still has a grant (shown in the permissions list).
Remember the 15-minute group cache.
See Permission errors for deeper troubleshooting.