Kieren _SmolSoftware_ Expert

FYI @Jake Ward , the Admin Automation app is publicly available now. It will allow you sync users from one group to another which could help with your IdP setup and getting users into Default Product Access groups. Hope the migration worked out for you! -Kieren Co-Founder @ Smol Software | Ex-Atlassian

FYI @Guy , the Admin Automation app is publicly available now. It doesn't have the 'remove inactive users' feature yet, but it's coming soon. -Kieren Co-Founder @ Smol Software | Ex-Atlassian

We've released an app to give admins some automation tools. In the case of customers with IdPs where they only want users to be granted product access via their IdP, you can sync users from an IdP group into your default product access groups. The Admin Automation app can automatically add or remove users from any group…

We've released an app to fix the issue of not being able to sync users into the default product access groups. The Admin Automation app can automatically add or remove users from any group into another group, and to solve other challenging and time consuming admin tasks. For example: * You can sync an IdP group into any of…

@Harold Price we've just launched. Hopefully it will solve your issue. https://marketplace.atlassian.com/1234013-Kieren Co-Founder @ Smol Software | Ex-Atlassian

Hi @ilaria.scagno The API will include app users too, but the UI filters those users out. If you filter out the connect app users, you’ll get the correct number. -Kieren Co-Founder @ Smol Software | Ex-Atlassian

Hi @john579taylor_gmail_com I've worked in this area for a long time, so I can give you some unique insights into this problem. 1. No, you cannot make a synchronised group be the default access group. As you've probably discovered already, you can grant product access to a synchronised group, you just can't make that…

Do you have one or more site names listed down your left menu? Can you tell us which products you have in each site? This could affect how the page works. Are you an Org Admin, or a User Access Admin ? You can double check this from the user list and searching for your name. 

So to be clear, when you visit admin.Atlassian.com : 1. the user doesn’t appear in your “users” list page, and 2. the user doesn’t appear in your “managed accounts” list Correct? If the user isn’t in your managed accounts list, then I expect their email domain is likely managed by another organization. You’d need to…

Thanks for the extra info @Mariam Omran. There are two possible paths for you, depending on if the user is suspended or deactivated: If they're suspended, this means they're already in your site but just suspended: 1. Go to admin.atlassian.com 2. Find the user in the user list 3. Open the user and 'Restore' their access.…

Hi @Dorindo You'll need to talk to your Trello Admin about this user and why they're inactive. Maybe the user needs to be reactivated, or there's a special process in your organization to activate a user, your Trello Admin will know more. Good luck. -Kieren Co-Founder @ Smol Software | Ex-Atlassian

Hi @Sunny Deol In admin.atlassian.com, you'll see a list of users. In that list you'll see Nahid. If they've not used Jira before, they should be listed as 'Invited'. From that list, you can resend an invitation. If Nahid still doesn't get an email invitation, they have one more option available to them: 1. They can go to…

Hi @Limber Lopez @John Funk is right, just make them a Jira Administrator. Go into admin.atlassian.com. Open the user you want to make a Jira Administrator, press the 'Grant access' button and select the Jira Administration product option. -Kieren Co-founder @ Smol Software | Ex-Atlassian

Hi @Mariam Omran Can you give some more details on what error comes up when you try to reactivate a user? There are a few things that come to mind which might prevent a user from being reactivated, but without more information I can't be sure if they're applicable to you. As for granting product access to a deactivated…

Hi @Marcy Grutza It's the start of the URL you use when you visit your Jira or Confluence product. The main URL will end in atlassian.net e.g. smolsoftware.atlassian.net Good luck -Kieren Co-founder @ Smol Software | Ex-Atlassian

Hey @Phil Grove Happy to chat about it. -Kieren

Hi @yamaguchi ayana The error means that your Atlassian org is not on the new User Management experience and you cannot use that API. Your options are: 1. Contact Atlassian support and ask if they can put your org onto the new experience. 2. Create a new Org and new products, these will automatically be on the new…

Hi @Fptsupport It sounds like you’ve added your email domain (@xyz.com) to the user access setting area (see https://support.atlassian.com/user-management/docs/control-how-users-get-access-to-products/). Then, when users try and visit your site (xyz.atlassian.net) they get this error screen? This error screen appears when…

For large customers, Atlassian support have been known to help in these situations, but it’s really dependent on each customer and there’s no guarantee they can actually do anything. As you said, their policy is first come first served. There are other policies that might be used to help tho, such as removing sites that…

Hi @bhumika.ray You could do a few things: 1. Deactivate 300 users. If there’s no active user, you won’t get billed. 2. Remove all product access from 300 users in your org. To bill for Atlassian Access, a user needs to be both provisioned and have access to a product in your org. 3. Add 300 users to your non-billable…

Hi @bhanu_kumarin_ext You might find this blog post helpful: https://smolsoftware.com/blog/3-ways-to-save-on-your-atlassain-bill Good luck -Kieren Co-Founder Smol Software | Ex-Atlassian

"Azure Connect for Nested Groups" - I've not heard of this tool before. Is this an App that has been installed from the Atlassian Marketplace? If you're referring to how Atlassian Access is setup here, then you'd need to select "Sync all users and groups" to avoid having to select each new specific group you need to sync.…

Hi @Rita Nygren Just so I understand the current process: Your service desk team will create new groups in Azure. Those new groups get sync'd to your Atlassian Org via SCIM. They then contact you to update various confluence space settings to include these new groups. Is that about right? I think you have two options: 1.…

For our customers we practically always create "default-do-not-use" group and assign that as the default group, and treat appearance of any user in this group as processes being broken (admins using invite functionality instead of relying on IdP to do its job) This is a great idea, I'll suggest it to others too. Thanks @Ed…

Hi @Gary Williams 1. Yes, this is a unique group that is created the first time you sync your IdP. It has the unique set of all the users you're syncing to the Atlassian directory. 2. This has been an issue for a while and unfortunately there is no feature within admin.atlassian.com that will allow you to sync an IdP group…

It depends on your setup. Adding a user to the site-admin or org-admin group may also give the user product access (increasing your bill). You could avoid that by removing product access from the site-admin or org-admin group. But that would also mean other user in that group lose product access. Those other admin users…

@Roof Mot if your account is managed, it could be marked for deletion by an admin within your organisation. You should be able to check the validity of that email by going to https://id.atlassian.com/manage-profile and checking if your account is managed and/or marked for deletion. You can read more about deleting…

Hi @Nick Block I don't have any information on how to do this for Bitbucket specifically, but I can help with how to do it within admin.atlassian.com. And if you're in one of the beta customer groups that get to link their Bitbucket product with their admin.atlassian.com org, then this would also work for your Bitbucket…

Another, less conventional option, is to create a new org admin user with a shared email account, such as AtlassianAdmin@yourdomain.com. Make them an organisation admin in your Atlassian Org. Then use that shared email address to control email forwarding to other users, or use it to forward the access requests to another…

To add to @Rebekka Heilmann _viadee_'s answer. The user would also have to be put into a group that granted them product access, as just creating the user isn't super useful. This could be done by calling one of the Jira APIs.