Limit visibility to single projects without changing access level

[Patrick R.]

I am struggling for words to either search for something like this in the community or come up with a good summary so anybody understands, so please let me explain what I am thinking of:

I have a colleague who has access to a few projects we are developing for different customers. Let's say projects A1 und A2 for customer A and project B1 for customer B.

This colleague needs to keep access to all three projects. To this point everything is working fine.

But when this colleague calls customer A and walks him through the backlog with his screen shared, there a some points where customer A will learn what we are doing for customer B. For example when my colleague types something into the search bar there is a list of projects to filter and some of them not for the customer seeing the screen at this moment.

So my question would be:

Is there any way how my colleague is able to use some kind of "aliases" or "content switch" or such, to say "okay, now show me only the project B1 but nothing else, no matter where I am clicking and typing"? And when he is done with sharing his screen with customer B he switches either to his "alias" for customer A oder back to his regular "see everything alias".

I highly doubt that this is achievable without any plugins. But as I mentioned above I am lost for the correct words. So if anyone could point me into the correct direction I would be very thankful.

Beste regards,

Patrick

[John Funk]

Hi Patrick - Welcome to the Atlassian Community!

One option might be to create a "dummy" user (or two to save you time). Grant one user access to Projects A1 and A2 and the other user Project B. You will need different email addresses but you should be able to create some gmail accounts for that. 

You can make the users inactive when not using with customers to not take up licenses if need be. 

Then have your colleague log on as User A when sharing with that customer or User B when sharing with that customer. 

[Patrick R.]

Hi John,

thanks for your answer and I am sorry for responding this late.

I had an similar idea to what you are suggesting before asking this question. I still called out to the community as this seems quite a somewhat annoying workaround.

In our case there wouldn't be only one colleague who needs to handle this situation but a few. Counting in vacation replacement and that the colleagues would need a primary account with all projects available I would need to add at least 12 new accounts, just for managing the currently available projects. And we are still moving the old ones to Jira. Switching them on and off every few days doesn't sound much appealing :(

I didn't put up these additional information in my initial question, so there is no way you could have known. So I thank you very much for your idea but I still hope that there is another approach out there waiting for me ;)

Best regards,

Patrick