![]() ![]() Under Options, select Disable Account.On the Managed Users screen, select Edit Account for the account you want to disable.(You must be an organization admin to manage users' Atlassian accounts.) To disable a user's Atlassian account in Atlassian Acccess Individual site administrators manage the users for the products on their specific Jira and Confluence sites, we recommend collaborating with your organization's Site Administrators before disabling managed users. You can always re-enable a user's account later from the managed user screen. This action will prevent the user from accessing any cloud applications and services (my.,, ).ĭisabled accounts will not count towards your Atlassian Access bill. Under options, select Disable account.On the managed users screen, select edit account for the account you want to disable.To disable a user's Atlassian account in Atlassian Access Please note, disabling a user will also remove the user from using that Atlassian account to raise technical support tickets, access their my. account,, and other free services. ![]() We recommend collaborating with your organization's Site Administrators before disabling managed users.Īs an organization admin, you can disable a user's Atlassian account to remove their access from Atlassian applications. Individual site administrators manage the users for the products on their specific Jira and Confluence sites. If you don't want to pay for certain members, make another policy non-billable and add them to it.įor more information, please see Understanding Authentication Policies.Ītlassian Access is billed when a managed account has access to any of the supported products: Once you do its members may count towards your Atlassian Access bill.Ī default policy can’t be a non-billable policy. You can easily update your policy back to all security settings. ![]() Add users that you sync from your identity provider (e.g., Okta, Azure AD, G Suite) to the policy.When you edit authentication policies and make a policy non-billable, you won't be able to: A non-billable policy has limited security for its members. You can only create a non-billable policy with a subscription to Atlassian Access. You can only have one (1) non-billable policy. We won't bill you for members in a non-billable policy. With a subscription to Atlassian Access, you can use a non-billable policy when you don’t want to pay for certain users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |