We're currently trialling Atlas for our project comms and it appears as though anyone with access to Atlas has full edit access to everything - the most problematic of these is that they can set themselves as a 'contributor' for any project, and they can 'archive' any project.
Am I missing a config step or is this by design? If it's intentional then it's hugely limiting.
My expectation is that someone who's only signed in to "follow" a project for updates shouldn't be able to edit the project they're following, they should only be able to comment on updates or raise questions, etc.
I'm having this same issue today (13.01.2024).
A random account just add itself to my Atlas without the need to request for permission. And then it starts requesting access to Jira, Confluence, etc.
The reason was that I used SimpleLogin email alias as login account (@simplelogin.com). The random account was also an email alias (atlassasian.3ktcr@simplelogin.com). I guess the system "assumes" we have the same domain, thus, from the same company.
This definitely should not be the default setting for Atlas.
Just giving a nudge on this in case anyone has an official answer. I'm assuming it's just not been considered, but would be nice to know if it's on any kind of roadmap to change in the future?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.