Kieren _SmolSoftware_ Expert

When I navigate to the Users section and click on the three dots next to a user Hi @Vitalii Marchenko You need to click into the user and open their details. Then you'll see the three dot menu in the top right of their details screen.

Hi @서영훈 When you go to admin.Atlassian.com do you have access to view the Users list? Or perhaps if you navigate to products then click on the site name in the left menu you’ll see the user list for a single site?

Hi @Rajendran, Jayanthi There are a few APIs you can use to add users to groups, this would give the most control over group/product access. https://developer.atlassian.com/cloud/admin/organization/add-user-to-group/ Another option would be to use an app like Admin Automations, that does all that for you. Generally what…

Sorry @d_b_kumar_chauhan but there’s no such API available.

Hi @Udo Marx It’s safe to rename a group. Atlassian checks if the group can be renamed before processing the new name. -Kieren Co-Founder @ Admin Automations | Ex-Atlassian

They could, absolutely. That’s the same as option 1. If it’s just one group that has all the users you want to grant access to, then just apply product access to that one group. But make sure you include that group in any project or global permissions you need to use. Instead of getting an invite, you should just include…

Hey @Matthew.Bonanno I think you have three options: 1. Choose some of the sync’d groups that you’ve created in the Atlassian Directory, and assign them product access to the products you want. The pro of this is you’re maintaining product access directly from your sync’d groups. The cons are; you’ll need to monitor for…

Hi @Matthew.Bonanno Are you on Cloud or DC?

Have you pressed the “resend invite” button in user management? Of their email address or domain is blocked by Atlassian, this button will unblock it and resend the invite.

We changed our group name to atlassian-JSM-agents. When I look at that group, it has 72 members. I can't figure out where the discrepancy lies between what our billing preview says and what I think it should say. Your discrepancy can come from a few places: 1. Org or Site Admins - Typically the site-admin or org-admin…

Be careful with removing users solely based on their last active date. That date/data is notoriously inaccurate. It only captures certain events the user does, so depending on how they use the product they might be marked incorrectly as inactive. E.g. org admins are less likely to go into a product like confluence, but…

Hi @Rebecca Lewis There’s no way to group groups together like you’re after. Here are some alternatives: 1. Name the team groups to include the department structure; e.g. mkt_sales_staff and mkt_sales_managers, eng_jira_devs, dept_team_A This obviously will take a lot to maintain, but it’s simple and cheap to implement if…

Hi @Trakadas, Pete SOPT You can change the User Access settings under admin.Atlassian.com -> Products, to remove the domain or product that users are requesting access to. And/Or add a message in there to direct users to the correct way to request access, via an email to you or another process you have? A good question to…

@Sarp Egemen is correct. Deactivated and suspended users do not count towards your bill. Also, if a user is in your user list and they do not have product access to confluence, they will not count towards your bill.

Hi @Vidya VASUDEVAN There are really only two options: 1. You can use the Atlassian APIs and write a bulk script yourself. 2. You can use a Marketplace App that allows you to bulk move users. There are plenty out there and most of them have 30 day trial periods, so plenty of time for you to use it and remove the app if you…

I can help further, but might need more information on your JSM project settings. Would you mind emailing me at kieren@smolsoftware.com ?

These users cannot be both Customers and Agents. Remove the JSM Customer toggle and see if that works?

The is an API that allow you to add users to groups: https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v1-orgs-orgid-directory-groups-groupid-memberships-post Another option is to use an app like Admin Automations to add users to groups.

That sounds like a good solution. Two things to note: 1. If you're granting the JSM Customer role to a sync'd Okta group, then make sure there's no Jira/JSM settings you need to configure that would normally use the JSM Default Groups. I think for JSM Customers you'll be fine, but it's something worth checking if you have…

Hi @Kyle Pontis Do you need to have the customers created as 'Customer Accounts' in JSM? Or are you happy to have the customers created as 'Atlassian Accounts' and granted customer roles within JSM? If you're ok to have the customers created as Atlassian Accounts, then just sync the users from your IdP into a single group,…

Nice write up @Darryl Lee. FYI, 'isVortexed' refers to whether the site is on the new user management experience (True) or not (False). Vortex was the project name for creating the new user management experience. -Kieren Co-Founder @ Admin Automations | Ex-Atlassian

If you’re happy to pay for the extra licenses for approvers, then make the approvers JSM agents, that’s certainly the simplest way. Then they can approve the ticket via JSM, they can get email notifications, you can use automations for a bunch of stuff too. Your options are very limited if you don’t want to make them…

Ahh ok, I understand. Customers and Users are different types of accounts. Customer Accounts within JSM cannot be added to groups. A way around this is to add or invite your customers to JSM as actual users, with the customer role. 1. Go to admin.atlassian.com, click on the Products menu, then on your site name, than on…

Hi @Amanda Gray By “group”, do you mean you’re going into admin.Atlassian.com and the Groups menu to add users into the Approvers group? And you can see the non-licensed users in the Users list on admin.Atlassian.com? I’m just double checking that I understand how you’re attempting to add users to the group.

Hey @Nand Patel @Tomislav Tobijas has the best solution if you’re comfortable with using the APIs. Another possible solution is to use an app like Admin Automation to automatically add users to groups, though I’m not sure where/how you’re storing the distribution list. -Kieren Co-Founder @ Admin Automations | Ex-Atlassian

The billing preview page takes longer to update numbers, potentially hours longer.

You may be able to just rename the group? Under the Group details in admin.Atlassian.com , and inside the three dot menu, you should have “Rename group” as an option.

The User you’re trying to do a password reset for needs to log into your jira or confluence product at least once before you can reset their password. This is a security feature to stop random sites from inviting you and resetting your password. The user can reset their own password too.

Hi @Patrick Matthews You mention you've already spoken to Atlassian Support. I don't think there's anything we can suggest that would be more helpful than what they can do. If it's a bug, then their Billing team and Devs will need to look in to it. If you only have confluence premium on your site, one thing you could try…

SCIM sync is certainly one of our main use cases, but it’s not the only one. I’m interested in knowing more about your use case, how would you want to automate the users being added to groups? Is there an attribute on the user or the jira ticket (like a group picker) that determines which group to add the user to?