I'm spinning up a new team to manage a new ATS contract.
We've begun the procurement process and are starting to build a backlog or requirements.
One of the bidders is our current provider, for obvious reasons i need to ensure they do not have access to the new board.
I've created a new board and tried to ensure that only a few can access it. I've run a few tests and so far everyone can access it.
I've followed advice from posts that I've found in this community, but I've been unsuccessful.
I'm assuming you're talking about a project board, and not a dashboard. With project boards there are type sharing areas that you'll need to manage for this; the "share" options in the board's general settings, and the "share" options on the associated issue filter.
The "best practice" configuration for the type of sharing you're describing would be to share the filter with the desired project & same for the board, rather than sharing with users/groups, which means accessing the board & filter should depend on your ability to access the project.
Hopefully this helps to answer your question.
In rereading your question, I'm now realizing you're saying that those who shouldn't have access to said board are admins on your instance...is this correct?
If so, then just the sharing alone won't prevent that, as admins have special access...in which case, you'd want to use issue-level security, per John's reply.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events