Not allowing customera to use the portal to which they have a link and added to the jira project

Vera Valshonok April 2, 2024

Hi, Community!

 

I have a project in jira which was used actively by customers. Now we have migrated the project to the other jira site, but customers still have access and use the previous site portal because we still have a project there where they were added previously and would like to keep it there.

How can we close ability to use the portal on the original site for the customers?

 

Is its impossible to do, is there a way to delete customers from a project in Bulk?

 

Thanks in advance!

1 answer

1 accepted

2 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 2, 2024

Hi @Vera Valshonok ,

Here are some options:

  • archive the project in the old instance if it is not needed
  • update permission scheme - settings > issues > permission schemes, find your project's scheme and update the permissions to remove Service Project Customer - Portal Access from Browse. Important don't do this if the scheme is used in other projects where you wish to retain browse access.
  • hide all Request types from portal
  • remove customers from the project or instance. Note that there is not a quick bulk remove.
Vera Valshonok April 2, 2024

Thanks a lot for the detailed answer! If we still need this project to not be lost and exist , can we archive it and then restore when customers will be more clear that they need to use the other site (as they wont be able to u se old one)?

How long a project can stay in archive without being automatically deleted?

 

  • hide all Request types from portal - all the request types in the project i want to lomis access to? what if we use only one request type in this project? 
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 2, 2024

You can archive for as long as you want. Here are my recommendations:

  • if neither Agents nor customers need access then archive.
  • if agents need access but not customers BUT these customers need access to the old issues then hide the request types so that customers cannot create new issues
  • if agents need access but not customers AND these customers do not need access to any other project in this instance then remove customers from the instance altogether.

in any event, if this instance should no longer be accessed now or in future you should ultimately remove customers.

Like Vera Valshonok likes this
Vera Valshonok April 2, 2024

Thanks a lot! We will remove all customers from the project as they don't need access from this restricted project anymore and agents need.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events