Manage Portal-Only Accounts in JSM Cloud: Revoke Access & Delete Impact

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

Revoking access or deleting an account prevents portal-only customer accounts from accessing the help center. Understand the consequences of each option.

  • Only organization admins can delete portal-only accounts.

  • The portal-customer search supports email addresses only, not names — use the exact email to locate an account.

Solution

If you want to…

Choose

Reversible?

Temporarily block portal access but keep the account & all references

Revoke access

Yes — re-grant anytime; all previous user references are kept

Permanently remove the customer and free the email for a future brand-new account

Delete customer

No — 14-day grace period, then wiped; a re-invite creates an unrelated new account

Where to revoke access or delete a portal-only customer account?

In your organization at admin.atlassian.com, if the Users and Groups options are under the Directory tab (as in the example below), you have the improved user management experience. If you don't see this option in your portal, it may be due to certain site configurations or limitations in your user management experience. In such cases, ensure you are an organization admin or contact your organization admin for further assistance in accessing 'Portal-only customers.'

Atlassian Admin navigation: Users and Groups selected under Directory.
  • To access the required page with the improved user management experience, click Apps, choose the site name from the left menu under Sites, and select Portal-only customers under Jira Service Management.

  • Without the improved user management experience, access the page by selecting Jira Service Management under User management in the left menu.

  • When searching for portal-only accounts, note that the search functionality currently only supports email addresses, not names. Use precise email addresses for locating these accounts. For further troubleshooting, consult the 'Managing Portal-Only Accounts in Jira Service Management' resource or contact support if issues persist.

After reaching the Portal customers page, tap the three-dotted icon next to the corresponding user, then select either Revoke access or Delete customer.

If you encounter difficulties, such as duplicate accounts or a missing delete option, ensure you are using the correct email address to locate the account. Only organization admins can delete portal-only accounts. If the issue persists, contact Atlassian Support for assistance.

Portal customer options menu with "Revoke access" and "Delete customer" highlighted.

Revoke access consequences

  1. The customer will no longer be able to access the instance's customer portal.

  2. The user won't be searchable and selectable in the user-picker fields.

  3. The user's name will appear as "Username (Deactivated)" in the user-picker fields that previously displayed their name.

  4. The account will still be searchable in filters, however, only by its email address.

  5. The customer's portal-only account can be reactivated at any time on the same page by clicking the three-dotted icon and selecting Grant access. All previous user references will be kept. Note: Reactivating users without granting product access keeps their accounts active while avoiding license consumption.

Delete customer consequences

  1. The customer account will be completely wiped out, resulting in loss of access to the instance's customer portal. Note: Deleting an account follows a 14-day grace period during which the account can't be re-invited or expedited for deletion.

  2. The user won't be searchable and selectable in the user-picker fields.

  3. The user's name will appear as Former user (Deactivated) in the user-picker fields that previously displayed their name.

  4. The account isn't searchable in any filter.

  5. No reference is kept on the account's email address. If the same customer is re-invited to the instance in the future, it will be a brand-new account with no correlation to the previously existing account. Note: Email updates for accounts must be managed through the user's identity provider, not directly within Jira.

How to confirm it worked?

  • After revoking access, the name shows as Username (Deactivated) in user-picker fields, and the account is still findable in filters by email.

  • After deleting the customer, the name shows as Former user (Deactivated), and the account is no longer findable in any filter.

Updated on July 23, 2026

Still need help?

The Atlassian Community is here for you.