- ACCESS-822Support more synced attributes for SCIM User Provisioning
- ACCESS-1487Push Other Attributes from an IDP to Atlassian Cloud Managed Profiles
- ACCESS-1558IP Allowlist audit log to include incident and IP address of blocked requests
- ACCESS-2000Cannot unsuspend a SCIM provisioned account(if this account is previously suspended)
- ACCESS-2041Support additional attributes for Azure AD sync (Osync)
- ACCESS-2076Provide OTP (MFA) option to portal-only customer
- ACCESS-1287Ability to change maintenance window for Atlassian Access
- ACCESS-1550Grant site admins the option to manage API tokens access for unmanaged users
- ACCESS-800Ability to rename groups after they've synced to the organization from an identity provider.
- ACCESS-1002Enabling allow listing policies automatically blocks Atlassian's own IPs
- ACCESS-2375Ability to clear data from history of manually cleaned Sensitive data
- ACCESS-1575Allow admins to unlock a provisioned managed account temporarily and later on relink with the Provisioned data (API and UI option)
- ACCESS-1048IP allowlist on organization administration (admin.atlassian.com)
- ACCESS-1315Include support ticket information for Atlassian Support IP Policy in Security > IP allowlisting
- ACCESS-604Grant users synced from identity providers via SCIM application access by default
- ACCESS-1009Ability to control site/organization access for accounts via user provisioning
- ACCESS-1761Provide different verification methods for external user logins
- ACCESS-2040Support additional attributes for Google Workspace Sync
- ACCESS-2119Prevent file / attachment uploads from mobile Apps
- ACCESS-1784Azure AD Connect Notification for Expired Credentials
- ACCESS-1952Allow Multiple External User Security Policies
- ACCESS-1540Provide Organization Admins with granular control over managed Bitbucket accounts
- ACCESS-1653Organization audit logs should show more details for user invite events
- ACCESS-1915Allow External users login via IDP Application Dashboards when enforced with External SAML SSO
- ACCESS-905Provide a web UI to change the managed accounts' public name for organization admins
- ACCESS-668Allow organization admins to have full control over profile visibility settings
- ACCESS-797Ability to see which accounts do not have 2FA enabled in an organization
- ACCESS-977Ability to exclude or remove a site from User Provisioning (SCIM)
- ACCESS-1294Update the Okta cloud application to make Jira/Confluence/etc chiclets configurable per user or group
- ACCESS-1522Warn admins of potential atlassian_conflict accounts added by Google.
- ACCESS-1612Ability to selectively enable external user security for subset of external users
- ACCESS-2347Ability to have Trello Free users not count as billable for Guard
- ACCESS-1824Route SSO-enforced users to their IdP regardless of which option they select from the login screen
- ACCESS-1609Allow automatically redirected to SSO provider when logging into a site
- ACCESS-2372Update Atlassian Cloud App in Okta to include Loom
- ACCESS-2212Ability to have more granular control of the "data export block" for Jira and Confluence
- ACCESS-592Logging out of Atlassian account does not log out of SAML provider
- ACCESS-814Implement user and group provisioning with Trello
- ACCESS-953Identify managed accounts by their sync status in API and UI
- ACCESS-1259Add UI options for managing members of authentication policies
- ACCESS-1825External Users || Enforce MFA || Authenticator apps
- ACCESS-1871Improve error messaging when invalid users are entered during bulk upload to authentication policy
- ACCESS-2202Customization for Guard Premium's Data Classification Field in Jira
- ACCESS-2308Disable the "Remove user" button on the Users page UI for SCIM synced users.
- ACCESS-2327Enhance Audit Logs to Clarify Duplicate Entries for IDP Sync
- ACCESS-2342Providing the option to use Data Classification for automation rules in Jira and JSM
- ACCESS-2364Separate Data Export and File Download Blocking into Different Security Policies
- ACCESS-2367Guard Detect Alert User of Sensitive Data
- ACCESS-2368Guard Detect Integrate with Atlassian Analytics
- ACCESS-2366Managed Teams when connected with a Group should not take the name of the connected group
1 of 488