Ash Young Atlassian Team

Hi @Matthew Challenger I'm curious to know more about how your site and users are setup. If you had the time - i'd love to have a quick chat with you when it suits you? booking link Some questions on my mind: * How do you "organise" your teams on JSM?* Do you use "groups" from an IdP, or * Do you use the "teams" feature in…

Hi @Riley Sullivan We're looking into Free/Standard/Premium right now. Would love to hear how this feature might work for your site? I've also opened my calendar for F2F chats if you're up to speaking about your JSM site? You can book a time with this booking link 

Hi @andrew_pass We're looking into how this feature fits into Premium. Do you mind sharing how this feature could work for your site. I've also opened my calendar for F2F chats if you're up to speaking about your JSM site? You can book a time with this booking link 

Hi @Tim Eddelbüttel Yep! this is our first step into introducing customization into queues. Would love to hear about how you plan to use Priority group on your site?

@Ste404 @Regan Marshall In your example "jack@gmail.com" would be added to your IdP. When you have your IdP connected to your JSM site - you're able to refer to your IdP to authenticate "jack@gmail.com" then redirect to your help center after authentication is successful. An ideal configuration would have all your…

Hi @Earl Reyes I'm not clear on your specific scenario. Would you mind providing a more detailed example of how you and your clients use Jira Service Management and what functionality you're looking for? Thanks, Ash

Hi @JG Meillaud The Jira Service Management "Customer" role for Atlassian accounts does not make an account "billable" for Atlassian Access. You are able to use Atlassian Access SSO for all your - as you describe "internal" & "external" users. You do not need to use a Portal-only customer account for your "external" users.…

Hi @Sam Gilchrist @Mark Benson @Jeff Hoover @Mullin, Joe I apologise that the community post indicated there would be no changes required for admins. based on your feedback, we've identified that admins will need to update product access settings for SCIM synced "groups" See below What will I need to change for new users?…

Hi @Mullin, Joe I'd point you towards the "Approved domains" feature and check you've configured that users from your domain are provisioned the "Customer" role when accessing JSM. You can find more information here

Hi @Bharath Kumar Kappala Could you send me an email at: ayoung3 (at) atlassian.com Lets set up a time to speak.

Hi @Chris Tolley Can i confirm you're using "Approved domains" to provision uses with the "Customer" role? You can find details about "Approved domains" here

Hi Chris Schneider You're able to use "Approved domains" to provision the "Customer" role to users you sync from your Azure AD. You can find more details about how to use "Approved domains" here

@Mathieu Truchot correct, no need to verify the external customer account domains. We continue to recommend you keep your internal verified domain users in one IdP and your external customers in another (two in total).

Hi @Andrei Bacanu Currently there is no way to disable the transition to the new "Customer" role in JSM. I'm interested in understanding why you're looking to disable this new role? Thanks, Ash

Hi @Jason Freeze The issue you linked would be a separate feature request. That wouldn't be related to this new SSO feature.

Hi all! A quick update for those following this page - JSM external customer SSO is now available for everyone: more information in this post Getting access today We’re progressively rolling out to all JSM sites - if you’re looking to skip the queue and enable it today, you can send an email to…

Hi all! A quick update for those following this page - JSM external customer SSO is now available for everyone: more information in this post Getting access today We’re progressively rolling out to all JSM sites - if you’re looking to skip the queue and enable it today, you can send an email to…

Hi @Billy Votta When to use Atlassian Accounts We'd recommend using Internal Atlassian Accounts for any users you expect to also require access to other Atlassian products (e.g. Bitbucket, Confluence). These are likely the employees/technicians you mentioned. You're able to use your Atlassian Access subscription for SSO…

Hi @Viktor Malmberg All users will land on the following link: https://<site>.atlassian.net/servicedesk/customer/user/login After entering an email address - a user will be prompted to sign up if our JSM site detects they are a new user. They will be presented with the following link…

Hi @Ian Bekker As you're aware we're currently working on SSO for Portal-only Accounts. I'd be interested to hear if you'd still be creating customer accounts via API after we release the feature mentioned here Apologies if our release schedule resulted in UX issues for your users. We're still aiming to release to 100%…

Hi @Roy We've not made any changes to how you remove users from your Atlassian site. You can find instructions on how to suspend or remove users from your Atlassian site.

Hi @Chrissy Clements If you meet the following criteria and are interested in early access please send an email to: jps@earlyaccessprogram.atlassian.net Please include the following details in your email: * Name(s) of key contacts for EAP * Email(s) of key contact for EAP * Atlassian site details (<site>.atlassian.net) *…

Hi @Kalin U @David Drong-Reisch @Huw Evans @Nina Vehovec @Leon Oud @Frederik Krogh @Ian Bekker @Marta Mita @Wim Abts @Leon Roth @Geoff Mether _Togetha Group_ @DIrk Grobler @Oliver Nash @Matthew.Kent @[deleted] @Geovanny Lara @Paul Salcombe @Matthew Campo @Pavel Bushuyeu @Niles Wimber @Max Parrish @Julien Béchade I've…

Hi @Luca Perri Apologies for the delayed reply. Atlassian Accounts with the "None" role (No Product Access) won’t be able to raise support requests. The purpose of this role type is to explicitly restrict the specific user from JSM. If a user configured with "None", this represents a Administrator’s specific decision that…

Hi @LarryBrock The new Unified Authentication Experience is for Cloud only at this moment.

Hi @Lori If you have administrator privileges you are able to disable anonymous access to your Help Center. You are also able to restrict account creation to ensure no unauthorised accounts are created. You can find more information here on how to configure your Help Center.

@Todd Thomas Thanks for the detailed write up - these are some very valid uses for search and filtering ad-hoc scenarios. I'm definitely looking at how to scale how Queues should be governed when teams within JSM scale. I agree that having JSM's growth and expansion locked behind an admin creating a new queue isn't…

Hi @Rachmad Kusairi These improvements relate to JSM product access for your sites. There is no impact to your projects (whether you use Next or Old generation projects).

Hi @Wilson Jacobs You can view and change the JSM product access roles at https://admin.atlassian.com/ Provided you have administrator access you'll be able to change your user's product access. As mentioned in the blog post, these changes aren't live yet. We have a migration plan where current users that have "None" will…

Hi @Darren Pegg Any users that have the JSM "User (Agent)" role will incur a cost - these users have access to JSM's issue view and have access to handle requests on the JSM platform. As of today, we haven't rolled out the "Customer" role just yet. Right now, if you only need an Atlassian Account user to access the Help…