Kieren _SmolSoftware__ar1cj1 Atlassian Partner

Hi @Sean Millar Another approach is to use an app like Admin Automations (an app that I build) to add any user from a specific domain, e.g. client.com, into a specific group that you grant space access to, e.g. client-space-access. You could then use the User Access Settings to grant users from client.com access to your…

Hi @Dimitar I_ Dimitrov I see you got your answer already, but here's some workaround options until Atlassian makes bulk actions a priority... 1. Write a script using the Atlassian APIs and run it every so often. Honestly this isn't too hard with all the AI Coding options now a days. 2. Use an App, like Admin Automations…

Hi @Sanam Malleswari You've got two great ideas already, but I wanted to ask how your site came to have 8000 groups? Depending on your answer, there might be some processes or checks you want to do to ensure the groups aren't recreated (such as an IdP syncing/creating the groups) or to ensure erroneous groups aren't…

The Group page and the IDP management pages were built by completely different teams, on different databases, so it's reasonable that they have different API calls. Given the audit logs show the group was created, and you're unable to see the group in your Group List, I'd suggest contacting Atlassian support for more help.…

I've never tried it using the SCIM APIs sorry. Do you have the logs from the APIs? I assume they were successful?

Hi @spencmax From what I can see, it looks like you're doing all the right things. The SCIM groups should show up in your Groups list, and they should be available to add to your apps. Can you look at the Identity Provider status page and tell us what you see? Here's an example of mine. Do the logs indicate that a…

I think @Connor has the most direct solution. Another option could be to use a marketplace app like Admin Automation to suspend your guest users within the Atlassian user directory. Note: I build the Admin Automation app. e.g. You could suspend all users in a group. Or you could suspend all users with a particular email…

I actually just posted a relevant article to this discussion: SCIM Sync Limitations And How To Overcome Them

I've talked to a lot of Atlassian customers about their Group and Administration setups, here's my thoughts on it: For Product Access 1. It's usually easier and less hassle to only have one or two groups that grant access to a single product. This means fewer issues when it comes to granting access, but more importantly…

Hi @jessica_huebner 1. Yes you’re correct, you still need a non-azure group to be a default group. This will still be used for manual invites or if a user self joins via the User Product Access settings. The main benefit of re-using any of the default groups is they already have all the correct global/space/product…

For reference, here's the main page on what these roles do: https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/

Hi @Albert Salerno Easiest option is to use an app like Admin Automations. It’s built specifically for a use case like this. You can specify a particular user to add/remove from groups on a schedule. Only other alternative is to roll your own scripts using the Atlassian APIs. Good luck!

Hi @Jeff Young I can offer some ideas, but I'm not sure how useful they are without more info: Both the ideas work on the expcetation that you can add users to specific groups based on their attributes, and configure your projects to give those users access based on their locaion groups. e.g. create a 'location-usa' group…

The Contributor and User Access Admin roles are only unavailable via the User Access Settings screen. They can still be granted to users via the User Invite and User Detail screens (see images below). But, they have to be granted by an Admin. It's certainly less useful that these two roles are only able to be manually…

Hi @Steven Zeck Q1: If User is selected, does it automatically add each account to the <product>-users-<sitename> group (like jira-users-myorg) when users sign up? A1: Yes, that's correct. Q2: is it possible to configure via User access settings so that users are added to the jira-product-discovery-contributors-myorg group…

Hi @Colleen Gotling It sounds like JSM is setup for access to new users in the User Access Settings. You need to be an org administrator to fix this: 1. Go to admin.atlassian.com and navigate to User Access Settings 2. There may be one or more domains listed there. You’ll need to open each one. 3. When you open a domain,…