we have quite a large user base in our company's JIRA system and everything is set up in that way that a new user who is granted application access will be able to view all boards and their stories (the default user has these rights).
We now want to invite guest users on specific projects. These should be restricted to be able to view and edit only a certain project.
Can this be done without restructuring the whole access system?
You would find it better to remove the "application user can see everything", but there is a slightly higher maintenance way to do what you want.
Create a new group for "guests". Give that group access to *only* the project(s) they should have. Add that group into the "can use application" global permission, but not the old "can use" group.
This is higher maintenance because you're going to have to remove the guest users from the old "can use" group every time you create a new guest.
Unfortunately, It is not just the license cost; they are also charged for every add-on as well.
We are currently using Jira and another tool manage projects. Unfortunately, I've seen the number of projects increasing in the other tool and would like to stop it. I can get Jira to do everything the other tool does (. However, Smartsheet allows us to work with externals sources without adding a license.
We are a Manufacturing company who makes Pharmaceutical widgets. Our customer found a piece of metal in one of the 10,000 widgets we shipped them. As they start recalling the other 9,999 widgets, they ask us to audit our systems and processes to find the root cause and eliminate it.
I know this sounds like a Service Desk Issue but is actually a large undertaking that includes multiple businesses including the farmers that grew the widget dust that we make widgets out of so we create a project.
Our customer would not be doing any work but would like insights into the progress (think Kanban) we are making.
If you want to offer only a view permission you do this:
I think this should be enough
I think that some aditional info can help:
Can you use only one role, or a small quantity of them for all your customers with the same permission scheme for all your projects? If not, would it be too difficult to achieve?
Have you a too large quantity of permission schemes that would take a lot of time to change them?
A basic approach would be to create a new permission scheme with the browse permission only for internal workers and guest users (role) and then change the permission schemes in your projects.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs