Audit log activities database
Audit log tracks key activities that occur within an organization. These activities can be used to diagnose problems or answer questions related to configuring and troubleshooting your organization and Atlassian apps as well as to manage users and groups.
Understand which activities are available with which subscription plan.
The table below is not an exhaustive list and does not encompass all audit log activities from Atlassian Administration. We are actively working to include more activities and keep this list as current as possible.
The following table provides a list of activities arranged by categories. You can also use your browser’s find tool to quickly locate any part of the activity displayed in the Activity dropdown of the audit log.
If you are encountering problems following this documentation - please raise a support ticket.
AI generated actions
Activity | Description |
|---|---|
Confluence Page Generated AI Content | Confluence page generated AI content. |
Confluence Page Triggered Policy Violation | Confluence page triggered organization policy violation. |
Jira Work Item Generated AI Content | Jira work item generated AI content. |
Jira Work Item Triggered Policy Violation | Jira work item triggered organization policy violation. |
Anti Abuse
Activity | Description |
|---|---|
Detected Confluence malware and classified | Detected Confluence malware and classified malicious file attachments uploaded to Confluence using in-house and third-party detection tools, providing clear warnings before access and enabling admin review in the audit log. |
Detected Jira malware and classified | Detected Jira malware and classified malicious file attachments uploaded to Jira using in-house and third-party detection tools, providing clear warnings before access and enabling admin review in the audit log. |
Analytics actions
Activity | Description |
|---|---|
Added batch of foreign keys between schemas | Defined foreign key relationships connecting tables across different schemas in a single operation. |
Added batch of foreign keys between tables | Defined foreign key relationships connecting tables in the same schema in a single operation. |
Added batch of foreign keys in data source | Defined foreign key relationships within a specified data source in a single operation. |
Added foreign key between schemas | Defined a foreign key relationship between two schemas. |
Added foreign key to table | Defined a foreign key relationship in a table. |
Archived dashboard | Moved a dashboard into an archived state, making it read-only and preserving historical data. |
Connected data source | Established a connection to an external or internal data source for analytics. |
Copied chart | Created a copy of an existing chart within the workspace. |
Copied control | Created a copy of an existing control for use in other dashboards or charts. |
Copied dashboard | Created a copy of a dashboard, including its layout and content. |
Created chart | Created a new chart for visualizing queried or transformed data. |
Created control | Created a new control on a dashboard. |
Created dashboard | Created a new dashboard in Analytics for data visualization and reporting. |
Created dashboard subscription | Set up a scheduled email delivery of a dashboard to specified recipients. |
Created data share | Configured a new integration to read or export Atlassian data from the Atlassian Data Lake to an external system. |
Created data share credentials | Created credentials for secure access to data shares. |
Deleted chart | Deleted a chart permanently from the workspace. |
Deleted control | Deleted a control from a dashboard. |
Deleted dashboard | Deleted a dashboard permanently, erasing its configurations and content. |
Deleted dashboard subscription | Deleted an active subscription for scheduled dashboard delivery. |
Deleted data share | Deleted a data export integration permanently. |
Deleted data share credentials | Deleted stored credentials for accessing data shares. |
Disconnected data source | Deleted a data source connection, restricting further queries from that source. |
Downloaded chart | Downloaded a chart in a supported file format for offline use or sharing. |
Edited Atlassian Data Lake connection | Changed the app data or scope of data for an Atlassian Data Lake connection |
Exported dashboard | Exported a dashboard as a PDF, CSV, or JSON. |
Granted dashboard access | Granted user permissions to view, edit, or manage a dashboard. |
Granted data source access | Granted users permission to query or manage a data source. |
Moved chart | Reassigned a chart from one dashboard to another. |
Moved control | Reassigned a control from one dashboard to another. |
Moved dashboard to trash | Moved a dashboard to the trash, allowing for potential restoration before it’s permanently deleted. |
Published changes to custom dashboard template | Published modifications to a saved custom dashboard template. |
Published custom dashboard template | Created and shared a new dashboard template for reuse. |
Refreshed data source | Initiated a manual or automatic refresh to get the latest schema from a connected source. |
Refreshed data source schema | Updated the schema to reflect new, modified, or removed tables or columns from a data source. |
Removed dashboard access | Removed user or team’s access to a dashboard. |
Removed data source access | Removed a user or team's access to a data source. |
Removed foreign key between schemas | Removed a cross-schema foreign key relationship. |
Removed foreign key from table | Removed a foreign key relationship from a table. |
Renamed chart | Changed the title of a chart. |
Renamed control | Changed the name of a control. |
Restored dashboard | Restored an archived or trashed dashboard to active use. |
Updated chart | Updated the configuration, data, or visualization options of an existing chart. |
Updated dashboard | Modified a dashboard, including settings, content, or layout. |
Updated dashboard subscription | Updated the parameters, timing, or recipients for a dashboard subscription. |
Updated data share | Changed the included app data for a data share. |
Updated data source | Updated data source settings or connection details. |
Updated foreign key between schemas | Edited a foreign key relationship between two schemas. |
Updated foreign key in table | Edited a foreign key relationship in a table. |
App actions
Activity | Description |
|---|---|
App auto update attempt | Attempted automatic update of the marketplace and third-party app, but the update was not completed due to a system or configuration issue. |
App auto updated failed (permission required) | Attempted automatic update of the marketplace and third-party app, but the update failed due to missing required permissions for the operation. |
App disable failure | Attempted to disable the marketplace and third-party app, but the operation failed due to a system or configuration issue. |
App disable success | Disabled the marketplace and third-party app successfully, making its features unavailable in the application. |
App enable failed | Attempted to enable the marketplace and third-party app, but the operation failed due to a system or configuration issue. |
App enable success | Enabled the marketplace and third-party app successfully, making its features available for use in the application. |
App failed installation | Attempted to install the marketplace and third-party app, but the installation failed due to a system or configuration issue. |
App failed installation (unsupported protocol) | Attempted to install the marketplace and third-party app, but the installation failed due to an unsupported protocol or configuration issue. |
App failed uninstallation | Attempted to uninstall the marketplace and third-party app, but the operation failed due to a system or configuration issue |
App successful dependency installation | Installed all required dependencies for the marketplace and third-party app, enabling its full functionality. |
App successful installation | Installed the marketplace and third-party app successfully, making its features available for use in the application. |
App successful uninstallation | Uninstalled the marketplace and third-party app successfully. |
App update failed | Updated marketplace and third-party app and saved changes. |
App update success | Updated marketplace and third-party app with the latest version that is now active. |
Third-party app Confluence API request | Requested access to the Confluence API by third-party app. |
Third-party app Jira API request | Requested access to the Jira API by third-party app. |
Atlassian accounts
Activity | Description |
|---|---|
Canceled deletion of account | Stopped the scheduled deletion of an Atlassian account, retaining it’s personal data and app access. |
Changed email address | Updated the email address for an Atlassian account. |
Deactivated account | Disabled access to an Atlassian account, preventing login and access to any Atlassian sites with the account. |
Deleted account permanently | Deleted an Atlassian account, permanently erasing its personal data. |
Logged in to account | Logged in to an Atlassian account to access an Atlassian app or site. |
Logged out of account | Logged out of an Atlassian account. |
Reactivated account | Re-enabled access to an Atlassian account, restoring login and access to any Atlassian sites. |
Requested password recovery link | Initiated a password reset for an Atlassian account by generating and sending a password recovery link to the account’s registered email address. |
Reset password with recovery link | Changed the password for an Atlassian account using a password recovery link. |
Scheduled deletion of account | Initiated the account deletion process for an Atlassian account, disabling access to the account. |
Bitbucket Cloud project actions
Activity | Description |
|---|---|
Created project | Created a project to group repositories and manage related repositories. |
Created project access token | Generated a project access token to to utilize for API authentication and automation with repositories in the same project. |
Deleted project | Deleted a project and all associated repositories. |
Removed project group permission | Removed a group's access permissions from the project to restrict repository access. |
Removed project member | Removed a user from the project, revoking their access to all project repositories. |
Updated project | Updated project details or settings to reflect organizational changes. |
Updated project branching model | Updated the project's branching model to enforce consistent naming conventions across repositories. |
Updated project group permission | Updated a group's permission level to manage access to project resources. |
Updated project member | Updated a project member’s role or permissions within the project. |
Updated project merge strategy | Updated the merge strategy for pull requests to control how changes are integrated. |
Updated project pull request setting | Updated pull request settings to define default reviewers across all pull requests within that project. |
Bitbucket Cloud repository actions
Activity | Description |
|---|---|
Accepted request to transfer repository from workspace | Approved transfer of repository out of workspace. |
Accepted request to transfer repository to workspace | Approved transfer of repository into workspace. |
Added repository deploy key | Added a deploy key to a repository forread/write access. |
Added repository group permission | Added group access permission to repository. |
Added repository member | Added a user as repository member. |
Created repository | Created a new repository. |
Created repository access token | Created a new access token with scopes to allow controlled access via API. |
Created repository webhook | Created a webhook to a repository to trigger a notification when an event takes place. |
Created request to transfer repository from workspace | Created a request to move a repository out of the current workspace. |
Created request to transfer repository to workspace | Created a request to move a repository into the current workspace. |
Deleted repository | Deleted a repository. |
Deleted repository webhook | Deleted a webhook from a repository. |
Downloaded repository | Downloaded raw repository by a user. |
Rejected request to transfer repository from workspace | Declined a workspace request to move a repository out. |
Rejected request to transfer repository to workspace | Declined a workspace request to move a repository in. |
Removed repository deploy key | Removed a deploy key from a repository. |
Removed repository group permission | Removed a group’s access permissions to a repository. |
Removed repository member | Removed a user from a repository. |
Revoked request to transfer repository from workspace | Revoked a pending request to move out a repository. |
Revoked request to transfer repository to workspace | Revoked a pending request to accept repository transfer. |
Updated repository | Updated repository settings or details. |
Updated repository branch restrictions | Updated branch restrictions for a repository. |
Updated repository group permission | Updated a group’s access permissions to a repository. |
Updated repository identifier | Updated a repository’s unique identifier. |
Updated repository member | Updated a repository member’s permissions or details. |
Updated repository privacy setting | Updated a repository’s privacy (public/private) setting. |
Updated repository project | Moved a repository to a different project. |
Updated repository pull request settings | Updated pull request settings by changing reviewers, PR description, default tasks or which files to exclude. |
Updated repository webhook | Updated a repository by either changing desired URL or triggers for events. |
Bitbucket Cloud user actions
Activity | Description |
|---|---|
Activated Bitbucket account | Activated user account to enable access. |
Added Bitbucket app password | Added a new app password for programmatic access to the account. |
Authorized user GPG key | Authorized a GPG key and links to the user account for commit verification. |
Authorized user SSH key | Authorized an SSH key and links to the user account for secure access. |
Deactivated Bitbucket account | Deactivated a user account and disables access. |
Deleted Bitbucket two-step verification recovery request | Deleted a pending request for two-step verification recovery. |
Disabled two-step verification in Bitbucket | Disabled two-step verification for the user account. |
Enabled two-step verification in Bitbucket | Enabled two-step verification for the user account. |
Generated Bitbucket two-step verification recovery email | Generated and sends a recovery email for two-step verification to the user. |
Generated Bitbucket two-step verification recovery notice email | Generated and sends a notification email regarding two-step verification. |
Regenerated Bitbucket two-step verification recovery codes | Regenerated new recovery codes for two-step verification. |
Removed Bitbucket app password | Removed an existing app password from the account. |
Revoked user GPG key | Revoked a previously authorized GPG key from the user account. |
Revoked user SSH key | Revoked a previously authorized SSH key from the user account. |
Updated username | Updated user’s Bitbucket username. |
Viewed Bitbucket two-step verification recovery codes | Accessed two-step verification recovery codes by the user. |
Bitbucket Cloud workspace actions
Activity | Description |
|---|---|
Accepted invitation to workspace | Accepted a user invitation to join the workspace. |
Added member to workspace group | Added a user to a group within the workspace. |
Added workspace member | Added a user as a member of the workspace. |
Authorized workspace SSH key | Authorized an SSH key for use in the workspace. |
Created group in workspace | Created a new group within the workspace. |
Created OAuth 2.0 consumer | Created a new OAuth 2.0 consumer for the workspace. |
Created workspace | Created a new workspace. |
Created workspace access token | Created a new access token for the workspace. |
Deleted group from workspace | Deleted a group from the workspace. |
Deleted OAuth 2.0 consumer | Deleted an OAuth 2.0 consumer from the workspace. |
Deleted user invitation to workspace | Deleted a pending user invitation to the workspace. |
Deleted workspace | Deleted a workspace. |
Disabled 2SV requirement | Removed a requirement for users to have 2SV configured to access content within workspace. |
Disabled IP allowlist enforcement | Removed restriction from which authorized IPs the workspaces content can be accessed. |
Enabled 2SV requirement | Enabled requirement for two-step verification (2SV) for the workspace. |
Enabled IP allowlist enforcement | Enabled IP allowlist enforcement for the workspace. |
Installed application | Installed an application in the workspace. |
Invited user to group | Invited a user to join a group within the workspace. |
Removed member from workspace group | Removed a user from a group within the workspace. |
Removed workspace group permission | Removed a group’s permission from the workspace. |
Removed workspace member | Removed a user as a member of the workspace. |
Revoked workspace SSH key | Revoked an SSH key from the workspace that will also impact any automation configured to use the now revoked key. |
Uninstalled application | Uninstalled an application from the workspace. |
Updated application | Updated an installed application’s configuration. |
Updated group in workspace | Updated a group’s details within the workspace. |
Updated IP allowlist | Updated IP allowlist configuration for the workspace. |
Updated OAuth 2.0 consumer | Updated an OAuth 2.0 consumer’s details. |
Updated workspace | Updated workspace settings or details. |
Updated workspace group permission | Updated a group’s permission level in the workspace. |
Updated workspace identifier | Updated a workspace’s ID, thus changing a URL for all content hosted within that workspace. |
Updated workspace privacy setting | Updated a workspace’s privacy setting to public or private. |
Compass user actions
Activity | Description |
|---|---|
Changed Compass permission policy | Updated the permission policy within the Compass to modify user access levels according to organization requirements. |
Created Compass custom field | Created a new custom field to components for storing specific metadata or details relevant to team's processes. |
Created Compass incoming webhook | Created a unique webhook URL to receive and process events from external tools into Compass components. |
Deleted Compass custom field | Deleted a custom field from Compass components to streamline or adjust stored metadata. |
Deleted Compass incoming webhook | Deleted an existing webhook configuration to stop ingesting events from external tools into Compass. |
Edited Compass custom field | Edited the configuration or properties of a custom field assigned to Compass components to better align with current needs. |
Confluence user actions
Activity | Description |
|---|---|
Activated Confluence space alias | Activated a configured alias to make the space accessible. |
Added Confluence default space permission | Assigned default space permission to control access. |
Added Confluence content restriction | Added content restrictions to customize permissions at the site, space, and content level. |
Added Confluence global permission | Assigned global permissions to see which user groups and which types of users currently have access to Confluence instance and make high-level decisions about what they can do on it. |
Added Confluence space permission | Assigned space permissions which determine what people can do in the space. |
Archived Confluence Attachment | Archived an attachment to remove it from active use. |
Archived Confluence space | Archived a space to restrict edits and simplify workspace management without deleting content. |
Changed Confluence color scheme | Changed the site or space color scheme to update display and branding preferences. |
Changed Confluence favicon | Changed the site favicon to customize browser tab or bookmark identification. |
Changed Confluence global settings | Changed site-wide global settings that control Confluence configuration. |
Changed Confluence public link permissions | Changed access permissions for public links to determine who can view shared content. |
Changed Confluence public links default space status | Changed the default permission for public links in a space to control content visibility. |
Changed Confluence site logo | Changed the site logo to align branding across Confluence pages and spaces. |
Changed Confluence stylesheet | Changed a custom stylesheet to adjust page appearance or typography settings. |
Changed Confluence theme | Changed the Confluence theme to apply a new layout or visual style. |
Completed Confluence blog export | Finished generating the blog export package, making it available for download. |
Completed Confluence page export | Finished generating the page export file, which is now ready for download. |
Completed Confluence space export | Finished generating the space export file, making it ready for download or transfer. |
Converted Confluence page to blog | Converted a page into a blog post. |
Converted Confluence page to folder | Converted a page to a folder to organize nested pages or related content. |
Copied Confluence space permission | Copied permissions from one space to another to save time and prevent mistakes. |
Copied Confluence default space permission | Copied permissions from one space to another to save time and prevent mistakes. |
Created Confluence announcement banner | Created an announcement banner to display important messages. |
Created Confluence blog | Created blog post to share announcements, journal entries, status reports, or any other timely information. |
Created Confluence database | Created a database to store, structure, and manage content. |
Created Confluence inline comment | Added an inline comment to a specific section of a page for contextual feedback or discussion. |
Created Confluence inline comment from editor | Added an inline comment while editing content to highlight changes or request input. |
Created Confluence inline comment from renderer | Added an inline comment from the rendered page view to capture specific feedback. |
Created Confluence live doc | Created a collaborative live document that allows multiple users to edit and update content in real time. |
Created Confluence page | Created page that are the place to capture all important (and unimportant) information. |
Created Confluence page comment | Added a comment at the bottom of a page for discussion or feedback. |
Created Confluence space | Created a new space to group related pages and manage team or project documentation. |
Created Confluence space role | Created a space role to manage permissions and access. |
Created Confluence whiteboard | Created a collaborative whiteboard for visual brainstorming and idea mapping. |
Created Confluence workflow application | Created a workflow application to automate review, approval, or content publishing processes. |
Deleted Confluence blog | Deleted blog post to share announcements, journal entries, status reports, or any other timely information. |
Deleted Confluence database | Deleted a database and its associated data from a page. |
Deleted Confluence group | Deleted a group and its associated permissions. |
Deleted Confluence inline comment | Deleted an inline comment from a page. |
Deleted Confluence page | Deleted page that are the place to capture all important (and unimportant) information. |
Deleted Confluence page comment | Deleted a page comment. |
Deleted Confluence space | Deleted a space, including its pages, content, and settings. |
Deleted Confluence whiteboard | Deleted a whiteboard and all associated visual content. |
Denied Confluence page export | Blocked a request to export a Confluence page due to insufficient permissions or restricted content settings. |
Disabled Confluence public links | Disabled public link sharing to prevent anonymous access. |
Downloaded Confluence blog export | Retrieved a complete export package of the selected blog for local download and storage. |
Downloaded Confluence page export | Retrieved a completed export file of the selected page for offline access or archival. |
Downloaded Confluence space export | Retrieved a complete export package of the selected space for local backup or migration. |
Edited Confluence blog | Edited blog post to share announcements, journal entries, status reports, or any other timely information. |
Edited Confluence live doc | Edited a live document to update or refine collaborative content. |
Edited Confluence page | Edited page that are the place to capture all important (and unimportant) information. |
Emptied Confluence space trash | Deleted items from the space trash to free up storage and finalize removals. |
Enabled Confluence public links | Enabled public link sharing to allow external users to view specific pages. |
Enabled Confluence public links on page | Enabled a specific page to be shared publicly through a link. |
Finished Confluence async export | Completed an asynchronous content export operation for a space or page. |
Finished Confluence import | Completed the import process for Confluence content or space data. |
Finished Confluence import | Completed an import process to bring external content. |
Initiated Confluence blog export | Started the process to export selected blog content into a downloadable file. |
Initiated Confluence page export | Started the export process for the selected page to create a downloadable file version. |
Initiated Confluence space export | Started the process to export Confluence space content into a downloadable archive. |
Logged in to Confluence admin key | Authenticated with an admin API key to perform privileged configuration actions. |
Logged out of Confluence admin key | Logged out from an active admin API key session. |
Made request to API | Called a Confluence API successfully or with an error. |
Moved Confluence page | Relocated a page within a space or to another space. |
Reassigned Confluence space role in bulk | Reassigned roles across multiple spaces in bulk. |
Reassigned Confluence space role permission in bulk | Updated role permissions simultaneously across multiple spaces. |
Reattached Confluence inline comment | Reattached an inline comment to its original inline context. |
Redacted Confluence content | Removed or obscured sensitive information from Confluence pages to maintain data privacy and compliance. |
Removed Confluence content restriction | Revoked content restrictions to customize permissions at the site, space, and content level. |
Removed Confluence default space permission | Revoked default space permission to control access. |
Removed Confluence global permission | Revoked global permissions to remove which user groups and which types of users currently have access. |
Removed Confluence space permission | Revoked space permissions which determine what people can do in the space. |
Removed Confluence space permissions in bulk | Removed specific permissions from users or groups across spaces. |
Removed Confluence space role | Removed a role from a space’s permission configuration. |
Removed Confluence space role in bulk | Removed roles across multiple spaces at once. |
Resolved Confluence page comment | Resolved a page-level comment as resolved to indicate that feedback or actions have been addressed. |
Restored Confluence soft deleted space | Restored a previously soft-deleted space to make it active again. |
Set Confluence space permissions in bulk | Changed space permissions for multiple users or groups at once. |
Set Confluence space role in bulk | Assigned roles to several Confluence spaces in a single operation. |
Soft deleted Confluence space | Deleted a space with the option to restore later. |
Unarchived Confluence Attachment | Archived attachment for active access and editing. |
Unarchived Confluence space | Unarchived space to restore collaboration and editing capabilities. |
Updated classification level of Confluence content | Updated classification level of a page. |
Updated Confluence announcement banner | Updated the text, styling, or visibility settings of an announcement banner. |
Updated Confluence Attachment | Updated an existing attachment on a page. |
Updated Confluence content | Updated existing page content to reflect changes. |
Updated Confluence page comment | Updated a comment on a page. |
Updated Confluence public link content status in bulk | Updated the public link sharing settings for multiple pages or blog posts simultaneously. |
Updated Confluence public link space status | Updated the public link sharing permissions for all content within a specific space. |
Updated Confluence space | Updated space settings to customize the space name, icon, and features. |
Updated Confluence space logo | Updated space logo by uploading an image or selecting one from the gallery. |
Updated Confluence space owner | Updated space owner by changing who can administer the space, assign permissions, and manage space settings. |
Updated Confluence space role | Updated space permissions by assigning or revoking what users and groups can do in the space. |
Updated Confluence space team presence settings | Updated space access settings to control how people, groups, and guests can view or work in the space. |
Updated Confluence workflow application | Updated the configuration or structure of an existing workflow application. |
Updated default classification level of a Confluence space | Updated default classification level that applies to a new page, issue, or other supported entity until it's manually classified by a user. |
Viewed Confluence Attachment | Viewed the content of an attachment. |
Viewed Confluence blog | Viewed Confluence blog |
Viewed Confluence database | Viewed data stored in a database. |
Viewed Confluence page | Viewed Confluence page |
Viewed Confluence whiteboard | Viewed a whiteboard to review collaborative visual content. |
Connected sources
Activity | Description |
|---|---|
Accepted app connection | Accepted the app connection so the app can access apps. |
Completed app credential rotation | Completed rotating credentials for the app to keep your apps and services running smoothly. |
Created app connection | Created an app connection to integrate your cloud apps. |
Deleted app connection | Deleted app connection to remove access. |
Rejected app connection | Rejected the app connection to prevent the app from accessing data. |
Revoked app connection credentials | Revoked credentials for the app connection to stop access. |
Started app credential rotation | Started rotating credentials for the app. |
Custom domains
Activity | Description |
|---|---|
Activated custom domain | Activated a verified custom domain so users can access Atlassian apps with organization’s branded URL, according to configured DNS and security settings. |
Associated a custom domain with a product | Associated an approved custom domain with a specific Atlassian cloud app so its URLs and access endpoints use your organization-managed domain. |
Created custom domain | Created a new custom domain entry to begin verification, DNS configuration, and integration with Atlassian cloud apps. |
Deactivated custom domain | Deactivated custom domain without breaking fallback URL and redirecting to the default URL. |
Deleted custom domain | Deleted a custom domain configuration so it can no longer be used for app URLs or user access. |
Detected a threat for custom domain | Detected a security threat or suspicious activity affecting a configured custom domain, triggering protection or remediation actions according to organization’s policies. |
Removed an association of a custom domain with a product | Removed the link between a custom domain and a specific Atlassian cloud app so that app stops using that domain for access. |
Suspended custom domain | Suspended a custom domain configuration due to security, compliance, or configuration issues, temporarily preventing it from being used for app access. |
Encryption Actions
Activity | Description |
|---|---|
Completed CMK re-encryption | Re-encrypted all data protected by CMK using new key material provided by the customer, ensuring continued compliance and data protection. |
Completed instance provisioning | Provisioned and configured a new CMK-enabled instance, making it ready for secure data operations. |
Completed revocation | Completed revocation process. All CMK-sites are suspended with services shut down. |
Created encryption policy | Established a new encryption policy to define how CMK are used for data protection in Atlassian Cloud apps. |
Created GSAC misconfiguration ticket | Logged a GSAC ticket to address a detected misconfiguration related to key policy settings. |
Created GSAC revocation ticket | Logged a GSAC ticket to initiate the revocation process due to the loss of access to customer encryption keys. |
Deleted encryption policy | Removed an existing encryption policy, discontinuing its enforcement on associated data and services. |
Detected encryption account anomaly | Identified an unusual activity or configuration in the encryption account, triggering further investigation. |
Disabled encryption policy | Disabled an active encryption policy, suspending its enforcement on protected data. |
Enabled encryption policy | Activated an encryption policy, enforcing its rules for data protection across relevant Atlassian Cloud apps. |
Ended product suspension | Resumed normal operations after a product suspension related to encryption or compliance issues. |
Failed encryption policy validation | Attempted to validate an encryption policy but encountered errors, preventing its activation or update. |
Initiated CMK instance provisioning | Started the process to provision a new instance with CMK encryption enabled. |
Initiated CMK re-encryption | Started the process to re-encrypt data using new customer encryption keys, ensuring ongoing data protection. |
Initiated CMK restoration | Started restoring access to CMK-data. |
Initiated revocation in EPS | Started the revocation process for encryption keys managed through the EPS. |
Provisioning requested by customer | Received a customer request to provision a new CMK-enabled instance or service. |
Requested CMK re-encryption | Submitted a request to re-encrypt data using new customer keys. |
Requested CMK restoration | Submitted a request to restore data encrypted with CMK. |
Started product suspension | Suspended product operations due to an encryption or compliance issue, pending resolution. |
Succeeded encryption policy validation | Successfully validated an encryption policy, confirming its readiness for enforcement. |
Updated encryption policy | Modified an existing encryption policy to reflect new requirements or security controls. |
Focus user actions
Activity | Description |
|---|---|
Added focus area follower | Added a user as a follower to a focus area so they receive updates and can track changes related to that work. |
Added focus area permission | Added a permission to a focus area to control who can view or manage its work and related activity. |
Added Focus group permission | Added group permissions to control user access and actions for enhanced user management. |
Archived focus area | Moved a Focus area to an archived state, preserving historical data but making it inactive and hidden from active workspace listings. |
Connected site to Focus | Created a connection between an external site and Focus to synchronize strategic priorities and associated data. |
Created focus area | Created a new Focus area representing a strategic priority, including its attributes and position. |
Created focus area type | Created a new focus area type to map strategic priorities according to organizational requirements. |
Created focus area update | Created an update entry to a focus area, capturing progress notes, status changes and team insights. |
Created review report | Created a structured report summarizing outcomes or progress within a focus area. |
Created view | Created a new view to group multiple focus areas together. |
Deleted focus area | Deleted an existing focus area and its associated data permanently. |
Deleted focus area type | Deleted an existing focus area type, adjusting the strategic hierarchy and available categorization options. |
Deleted focus area update | Deleted a previously entered update, removing progress or commentary information from a focus area. |
Deleted view | Deleted a saved view, eliminating its custom filters from the workspace. |
Disconnected site from Focus | Removed the linkage between a site and Focus, stopping synchronization of data. |
Edited focus area | Edited details of an existing focus area, such as its type, owner, or targeted outcomes. |
Edited focus area type | Edited a focus area type’s definition or hierarchy level to improve alignment with organizational structure. |
Edited focus area update | Edited content within a focus area update to correct or clarify progress, status, or team insights. |
Edited view | Edited configuration options in a view, adjusting its filters, fields, or display format for better data presentation. |
Exported focus area | Exported a file containing details and data associated with one or more focus areas for offline analysis. |
Exported view | Exported the contents of a view, enabling sharing or further processing outside the Focus app. |
Imported data spreadsheet | Imported data from an external spreadsheet into Focus to enrich reporting and strategic tracking. |
Link a review report | Linked a review report with a relevant focus area, enabling consolidated tracking and visibility of review outcomes. |
Removed focus area follower | Removed a user as a follower from a focus area so they no longer receive updates or track related changes. |
Removed focus area permission | Removed a permission from a focus area to change who can view or manage its work and related activity. |
Removed Focus group permission | Removed group-level permissions, restricting access or capabilities in Focus. |
Unarchived focus area | Changed focus area to active status, making its details and updates visible and editable in the workspace. |
Unlink a review report | Unlinked a review report from a focus area, removing its association and related visibility within the strategic context. |
Goals user actions
Activity | Description |
|---|---|
Archived goal | Archived a goal, removing it from search results and stopping update reminders for owners. |
Archived metric | Archived a metric, stopping its updates and making it read-only to retain its historical records. |
Connected Slack to goal | Connected a goal to a Slack channel to automatically share updates and notifications with stakeholders in real time. |
Created metric | Created a new metric to track and evaluate goal progress in a structured and quantifiable way. |
Created metric value | Created a specific value for a metric, reflecting progress or status at a given point in time. |
Exported goals from workspace | Exported goal data in a chosen file format for offline analysis or external reporting. |
Updated metric | Updated the configuration or definition of an existing metric to adapt to changing requirements. |
Updated metric value | Updated the latest value of a metric to represent new data or progress updates. |
Updated workspace | Updated workspace settings or configuration to suit the organisation’s requirements. |
Home user actions
Activity | Description |
|---|---|
Added member to project | Granted a user access to the project, enabling collaboration and participation according to assigned permissions. |
Archived project | Moved the project into an inactive state while preserving data for future reference or audit needs. |
Connected Slack to project | Integrated a Slack channel with the project to enable real-time notifications and streamlined team communication. |
Deleted answer | Deleted a posted answer from the project’s discussion or knowledge base. |
Deleted comment | Deleted a comment from tasks, discussions, or project updates, ensuring content stays relevant and accurate. |
Deleted question | Deleted the selected question from the project’s knowledge base or FAQ, maintaining up-to-date project information. |
Exported teams | Exported team details. |
Exported users | Exported user information. |
Exported workspace projects | Exported a file containing project data from the workspace for external analysis, backup, or migration. |
Removed member from project | Removed a user’s access to the project, restricting their ability to view or contribute to project content. |
Jira user actions
Activity | Description |
|---|---|
Added Jira global permission | Granted a user or group new global permissions across your Jira site. |
Added Jira issue security level | Created a new security level to control who can view specific work items. |
Added Jira issue security level member | Added a user or group to a work item security level, managing their access to certain work items. |
Added Jira issue security scheme | Created a new work item security scheme to define visibility rules for work itemss. |
Added member to Jira project role | Added a user to a specific role within a Jira project. |
Associated Jira issue security scheme | Linked a work item security scheme to a project, setting visibility rules for work items within that project. |
Associated Jira project permission scheme | Connected a permission scheme to a project, defining user permissions for project actions. |
Closed sprint | Marked a sprint as completed and moves any unfinished work item to the backlog or next sprint. |
Copied Jira issue security scheme | Created a duplicate of an existing work item security scheme for reuse or modification. |
Copied Jira project permission scheme | Duplicated a project permission scheme to use as a template or for further customization. |
Created issue type | Defined a new type of work item for your Jira projects, such as a bug or feature. |
Created Jira issue | Created a new work item (task, bug, story, etc.) in your Jira project. |
Created Jira project permission scheme | Created a new permission scheme to manage project access and actions. |
Created screen | Created a new screen layout for work item creation, editing, or viewing. |
Created screen scheme | Created a new screen scheme to manage which screens appear during different work item operations. |
Created screen scheme item | Created a screen within a screen scheme, specifying when it should be used. |
Created sprint | Created a new sprint for a team’s work. |
Deleted issue type | Deleted a work item type from Jira project. |
Deleted Jira issue | Deleted a work item from a Jira project. |
Deleted Jira issue security level | Deleted a issue security level from a work item security scheme, changing which users or groups can view particular work items. |
Deleted Jira issue security scheme | Deleted issue security scheme that controlled who could view specific issues using defined issue security levels based on users, groups, or project roles. |
Deleted Jira project permission scheme | Deleted a project permission scheme that determined who can access and edit spaces, preventing it from being used to grant permissions across multiple spaces. |
Deleted Jira project role | Deleted a project role used by permission schemes to grant capabilities in a space, affecting how permissions are managed without granting unwanted access. |
Deleted screen | Deleted a screen layout from Jira configuration. |
Deleted screen scheme | Deleted a screen scheme from Jira project settings. |
Deleted screen scheme item | Deleted an item from a screen scheme, altering when certain screens are used. |
Deleted sprint | Deleted a sprint and its associated data. |
Edited Jira issue | Edited the details or status of an existing work item. |
Granted permission to Jira project permission scheme | Granted a permission in a project permission scheme to a user, group, or space role, controlling who can access and edit the associated spaces. |
Imported sprint | Imported a sprint and its associated data from another source or project. |
Removed Jira global permission | Removed global permission that applied across the entirety of the site, changing who can access Jira and what they can do in all existing projects. |
Removed Jira issue security level member | Removed a user, group, or project role from a issue security level, updating who can see particular work items. |
Removed member from Jira project role | Removed a member from a project role used in permission schemes to configure and reuse project permissions for specific users, groups, or roles. |
Removed permission from Jira project permission scheme | Removed a permission in a project permission scheme from a user, group, or space role, restricting who can access and edit the associated spaces. |
Started sprint | Started a planned sprint, allowing work to commence. |
Updated classification level of Jira issue | Updated the data classification level for a specific work item. |
Updated default classification level of a Jira project | Updated the data classification level that will be applied to any work items within the project that are not specifically classified. |
Updated issue type | Updated the settings or fields of an existing work item type. |
Updated Jira issue security level | Updated the issue security level to change which users or groups can view the issue according to the associated issue security scheme. |
Updated Jira issue security scheme | Updated issue security scheme that defines issue security levels to control visibility of individual issues for selected users, groups, or project roles. |
Updated Jira project permission scheme | Updated project permission scheme that applies project permissions and access levels to users, groups, or roles and can be associated with one or more projects. |
Updated screen | Updated the layout or fields of a Jira screen. |
Updated screen field | Updated the fields displayed on a screen. |
Updated screen scheme | Updated the configuration of a screen scheme. |
Updated screen scheme item | Updated when a particular screen is used within a scheme. |
Updated screen tab | Updated the tabs or layout within a Jira screen. |
Updated sprint | Updated sprint details, such as dates or goals. |
Viewed Jira issue | Viewed the details of a work item in Jira. |
Jira service management product actions
Activity | Description |
|---|---|
Connected with Microsoft teams | Connected Jira Service Management with Microsoft Teams for seamless collaboration. |
Connected with Slack | Linked Jira Service Management to Slack to streamline team communication and notifications. |
Connected with Zoom | Connected Zoom with Jira Service Management to enable direct meeting scheduling and collaboration. |
Created custom page in help center | Added a personalized page to your help center to share tailored information with customers. |
Created customer organization | Created a new customer organization to manage customers and permissions more efficiently. |
Created new help center | Created a new help center to provide centralized self-service support for customers. |
Created service | Created a new service to support team’s workflows and user needs. |
Created topics in help center | Organized help center by adding new topics tto help customers find relevant information quickly. |
Deleted a help center | Deleted a help center that is no longer needed, streamlining support resources. |
Deleted custom page in help center | Deleted a custom page from help center to keep content up to date. |
Deleted customer organization | Deleted a customer organization to maintain accurate and current customer management. |
Deleted service | Deleted a service that is no longer required, keeping workspace organized. |
Deleted topics in help center | Deleted outdated or unnecessary topics from help center for improved navigation. |
Disconnected from Microsoft teams | Disconnected Jira Service Management from Microsoft Teams, ending integration features. |
Disconnected from Slack | Disconnected Slack integration as a support channel. |
Disconnected from Zoom | Disconnected Zoom integration, removing meeting features from Jira Service Management. |
Edited custom page in help center | Updated a custom page in help center to reflect the latest information. |
Edited topics in help center | Edited help center topics to improve clarity and relevance for customers. |
Enabled HIPPA-compliant alert notifications | Enabled alert notifications that meet HIPAA compliance standards for secure communication. |
Removed service relationship | Disconnected a service relationship to update support or workflow structure. |
Updated a help center | Updated help center to improve customer experience and support resources. |
Updated announcement in help center | Updated help center announcement to keep customers informed of important changes. |
Updated auto-share requests with customer organization settings | Updated auto-share settings to better control request sharing with customer organizations. |
Updated compliance settings | Updated compliance settings to align with organization’s security and regulatory needs. |
Updated connection with Microsoft teams | Updated Microsoft Teams integration for improved connectivity and features. |
Updated customer access settings | Updated customer access permissions to enhance security and customer management. |
Updated customer login settings | Updated login options to provide a better and more secure sign-in experience. |
Updated customer notifications setting | Updated notification preferences to ensure customers receive relevant updates. |
Updated customer organization | Updated a customer organization to reflect current membership and permissions. |
Updated customer organization permission | Updated permissions for a customer organization to manage access. |
Updated customer permissions | Updated customer permissions to control access to portal and request sharing.. |
Updated global incoming email settings | Updated email settings to manage how incoming email requests are handled across organization. |
Updated help center project mapping | Updated project mapping in the help center to ensure accurate support routing. |
Updated help center settings | Updated help center settings to better meet support needs. |
Updated knowledge base global permissions | Updated global permissions for knowledge base to manage access, and support resources. |
Updated layout for custom page in help center | Updated the layout of a custom help center page to enhance readability and engagement. |
Updated layout in help center | Updated the help center layout for improved navigation and ucustomer experience. |
Updated name creation for SLA metrics permission | Updated permissions related to creating new SLAs for better workflow control. |
Updated portal visibility in help center | Updated visibility settings to control which portals are visible in the help center. |
Updated responder alert settings | Updated alert settings to ensure responders are notified promptly. |
Updated service | Updated a service to improve performance or reflect changes in service projects. |
Updated service relationship | Updated a service relationship to better align with support structure. |
Updated team management project creation permission | Updated permissions for creating team-managed projects. |
Jira service management project actions
Activity | Description |
|---|---|
Added customers to project | Added customers to a project to enable request submissions. |
Created a new request type | Created a new request type for categorizing customer requests. |
Created customer notification settings for team managed projects | Created notification preferences for customers in team-managed projects. |
Created JSM queue priority group | Created JSM queue priority group to organize requests by priority for teams. |
Created link as external resource | Created an external resource link related to the project. |
Created new customers | Added new customers to the service management system. |
Created portal groups | Created groups to organize your request types, making it easier for customers to find what they need in the portal.. |
Created Queue | Created a queue to organize and triage incoming requests. |
Created reports | Created reports to analyze project metrics and performance. |
Created SLA | Defined service level agreements to track response and resolution times. |
Created SLA calendar | Created calendars to manage SLA working hours and holidays. |
Created template form | Created reusable forms for standardized request submissions. |
Deleted customer notification settings for team managed projects | Deleted notification settings for customers in team-managed projects. |
Deleted JSM queue priority group | Deleted JSM queue priority group to remove an existing priority-based grouping. |
Deleted link as external resource | Deleted an external resource link from the project. |
Deleted portal groups | Deleted groups from the customer portal. |
Deleted Queue | Deleted a queue from the project. |
Deleted reports | Deleted generated reports from the project. |
Deleted request type | Deleted a request type from the project. |
Deleted SLA | Deleted a service level agreement from the project. |
Deleted SLA calendar | Deleted a SLA calendar from the project. |
Deleted template form | Deleted a reusable form template. |
Deployed form template in project | Deployed form template in project. |
Deployed form template permissions in project | Deployed form template permissions in project to control who can view or use. |
Exported form responses | Exported responses collected from forms for external use. |
Exported reports | Exported project reports for offline analysis. |
Invited team to project | Invited team members to join the project. |
Language added to project | Added a new language option to the project. |
Language availability updated | Updated the languages available in the project. |
Language removed from project | Removed a language option from the project interface |
Project customer satisfaction setting updated | Updated settings related to customer satisfaction surveys. |
Project default language updated | Updated the default language for the project. |
Removed customers from project | Removed customers from the project, revoking access. |
Turned off email support or disconnected custom email account | Disabled email request channel or disconnected a custom email account. |
Turned on email support or connected custom email account | Enabled email request channel or connected a custom email account. |
Updated change management deployment pipelines | Updated deployment pipelines for change management processes. |
Updated chat settings in Channels | Updated chat configurations within support channels. |
Updated customer notification settings | Updated notification preferences for customers. |
Updated customer notification settings for team managed projects | Updated notification settings for customers in team-managed projects. |
Updated customer organization membership | Updated membership details of customer organizations. |
Updated customer permissions | Updated permissions assigned to customers in the project. |
Updated email account settings | Updated settings for email accounts used in the project. |
Updated JSM queue priority group | Updated JSM queue priority group to change the configuration of how requests are grouped and prioritized. |
Updated knowledge base | Updated content in the project's knowledge base. |
Updated link as external resource | Updated details of an external resource link. |
Updated portal groups | Updated groups within the customer portal. |
Updated project features | Changed enabled features in the project. |
Updated project portal configurations | Updated configurations of the project portal. |
Updated Queue | Updated settings of a queue in the project. |
Updated reports | Updated existing project reports. |
Updated request types | Updated configuration of request types. |
Updated responder alert settings for projects | Updated alert settings for responders |
Updated SLA | Updated service level agreements. |
Updated SLA calendar | Updated SLA calendar settings. |
Updated template form | Updated reusable form templates. |
Updated virtual agent Atlassian Intelligence Answers settings | Updated settings for the virtual agent's AI answers. |
Updated virtual agent settings in Channels | Updated virtual agent settings within support channels. |
Updated virtual agent Standard Flow | Updated the virtual agent's standards flow configuration. |
Updated widget settings | Updated settings for the widget in the project. |
Loom system actions
Activity | Description |
|---|---|
Deleted Loom space video | Deleted a video from the specified Loom space, making it inaccessible to all users. |
Transferred workspace content | Moved all designated workspace assets and data to another workspace or user, maintaining organizational continuity and access. |
Updated Loom user status | Updated the current status of a Loom user within the workspace, adjusting their access and permissions. |
Updated privacy settings for Loom video | Updated privacy controls to a Loom video, adjusting who can view or share the content per workspace settings. |
Updated sales support type | Changed the assigned support category for sales requests, directing issues to the appropriate channel based on updated requirements. |
Updated workspace group | Modified the configuration or membership of a workspace group, ensuring alignment with organizational structure and user roles. |
Updated workspace group member | Changed the status, permissions, or membership of a user within a workspace group to reflect current access needs. |
Updated workspace status | Changed the operational or accessibility status of a workspace, reflecting any changes in activity, availability, or administrative state. |
Loom user actions
Activity | Description |
|---|---|
Added Loom space members | Added new members to the Loom space, granting them access to collaborate and manage available video resources within the space. |
Archived Loom video | Archived the Loom video, moving it from active listings to the archive for retention or later restoration as per workspace policies. |
Assigned space to workspace group | Linked the Loom space to a designated workspace group for streamlined management and centralized access controls |
Commented on Loom video | Added a comment to a Loom video to facilitate discussion or provide feedback for workspace collaborators. |
Created Loom space | Created a new Loom space for organizing and managing related videos and member access. |
Created Loom video | Generated a Loom video and stored it within the designated Loom space for team or project use. |
Deleted Loom space | Removed the Loom space and all associated content, revoking member access and erasing workspace records. |
Deleted Loom video | Deleted the Loom video from the Loom space and all associated access lists. |
Deleted workspace data retention setting | Deleted the specified workspace data retention setting, reverting to default compliance configuration for video content. |
Deleted workspace user | Revoked and deleted the user’s access from the Loom workspace, removing associated permissions and content ownership. |
Downloaded Loom video | Exported and saved the Loom video file for offline access or local review based on workspace permissions. |
Duplicated Loom video | Created a copy of the original Loom video, adding it to the designated space for separate editing or usage. |
Loom video password updated | Modified password protection on a Loom video to change access credentials and reinforce privacy controls. |
Reacted to Loom video | Added a reaction to a Loom video for quick feedback or acknowledgment within the workspace |
Removed Loom space members | Removed specified members from a Loom space, withdrawing their access to associated video content. |
Shared Loom video | Distributed a Loom video link or access permissions to designated recipients for collaboration or viewing. |
Unarchived Loom Video | Restored a Loom video from the archive to active status, making it available for workspace access and collaboration. |
Updated default workspace privacy setting | Changed the workspace’s default privacy configuration to define access levels for newly added content. |
Updated Loom space data retention setting | Changed data retention policies for a Loom space, adjusting archival and deletion schedules based on compliance needs. |
Updated Loom space privacy settings | Modified the Loom space’s privacy controls to manage member visibility and video access. |
Updated Loom video | Edited the Loom video’s metadata, permissions, or content within the workspace. |
Updated Loom video link expiration | Changed the expiration date for Loom video access links to enforce time-based availability. |
Updated Loom video permissions | Adjusted permissions on a Loom video to refine access and collaboration controls for workspace users. |
Updated Loom workspace video access | Updated video access in the workspace. |
Updated Loom workspace video owner | Updated the video owner in the workspace. |
Updated search indexing for Loom video | Refreshed search indexing for the Loom video to improve discoverability within workspace queries. |
Updated workspace content privacy setting | Modified privacy settings for workspace content, ensuring proper access levels and compliance controls. |
Updated workspace data retention setting | Adjusted workspace-wide data retention policies to align with organizational or regulatory standards. |
Updated workspace domain privacy | Changed privacy preferences for the workspace domain, affecting visibility of workspace content and user listings. |
Updated workspace integration | Modified integration settings for the workspace to enable or restrict connected apps and third-party access. |
Updated workspace link expiration setting | Changed link expiration preferences for shared workspace resources to control duration of external access. |
Updated workspace setting | Adjusted a general workspace configuration to update defaults or enable new management options. |
Viewed Loom video | Viewed a video in the workspace to easy to learn and stay on track. |
Operations Global actions
Activity | Description |
|---|---|
Activated auto-heartbeats | Activated auto-heartbeats to enable automated monitoring checks and system heartbeat signals for service health tracking. |
Added operations integration | Added operations integration to connect Loom events with external IT operations platforms for streamlined incident management. |
Added rules to integration | Added rules to integration to enhance event processing and automated actions within the integrated system. |
Added team | Added team to grant collaborative access and manage user permissions in Loom workspace. |
Created alert | Created alert to establish automated notifications for specified service events or anomalies. |
Created alerts filter | Created alerts filter to refine notification criteria and prioritize relevant alert signals. |
Created custom role | Created custom role to define tailored access permissions for users in Loom environments. |
Created maintenance | Created maintenance to schedule and manage periods of planned service downtime or updates |
Created role-based notification | Created role-based notification to deliver alerts according to specific user roles and responsibilities |
Deactivated auto-heartbeats | Deactivated auto-heartbeats to halt automated system health monitoring signals. |
Deleted alert | Deleted alert to remove a specified notification from the active alert list. |
Deleted alerts filter | Deleted a criteria-based rule that managed or suppressed notifications. |
Deleted custom role | Deleted a tailored permission set from operational access controls. |
Deleted maintenance | Cancelled a scheduled system update or maintenance window. |
Deleted role-based notification | Removed notification rules previously assigned by user roles. |
Deleted rules in integration | Deleted specific automation or routing rules from the operations integration. |
Deleted team | Deleted a group from operational access or notification lists. |
Edited alerts filter | Modified the criteria or logic that determines which alerts are shown or suppressed. |
Removed operations integration | Disconnected an external operations tool and terminated its workflow automations. |
Updated alert | Changed details or escalation rules for an existing notification. |
Updated custom role | Edited permissions or user assignments for a tailored operational role. |
Updated maintenance | Changed the schedule or details of a planned maintenance window. |
Updated operations integration | Modified settings or connection parameters for an external operations tool. |
Updated role-based notification | Changed rules for how notifications are sent based on user roles |
Updated rules in integration | Edited automation or incident routing logic within the operations integration |
Updated team | Changed membership or team configuration for operational resources. |
Updated user roles | Modified the permissions or assignments for user operational access. |
Operations Team Actions
Activity | Description |
|---|---|
Added custom team role | Defined a unique permission set to tailor team member responsibilities within the team structure. |
Added escalation policy | Configured a response sequence to prioritize and route incidents to appropriate team members. |
Added on-call schedule | Established a shift pattern assigning team members to incident response availability windows. |
Added override | Set temporary adjustments for on-call schedules or incident responsibilities. |
Added rotation | Structured on-call assignments to rotate responsibilities among team members. |
Added team alert policy | Implemented rules governing how alerts are managed and escalated for the team. |
Added team heartbeat | Enabled monitoring checks to verify team system health and operational status. |
Added team member | Assigned a user to the team to participate in operational workflows and notifications |
Created routing rule | Established criteria for directing alerts or incidents to the appropriate team members |
Deleted custom team role | Removed a unique team-specific permission set from the team’s configuration. |
Deleted escalation policy | Removed an incident routing sequence from the team’s operational setup. |
Deleted on-call schedule | Eliminated an assigned shift pattern for team participation in incident response. |
Deleted override | Cleared a temporary adjustment made to the standard on-call or incident schedule. |
Deleted rotation | Removed a rotating schedule from the team’s on-call assignments. |
Deleted routing rule | Removed a defined process for directing incidents or alerts to specific team members. |
Deleted team alert policy | Removed rules that governed how team alerts were handled or escalated. |
Deleted team heartbeat | Disabled regular health check monitoring for the team’s systems or services. |
Removed team member | Unassigned an individual from the team’s operational roles and notifications |
Updated custom team role | Modified the responsibilities or access granted through a team-specific permission set. |
Updated escalation policy | Edited how incidents are prioritized or routed within the team’s response workflow. |
Updated on-call schedule | Changed the assigned shift pattern or availability windows for team members. |
Updated override | Modified a temporary schedule or responsibility adjustment for the team. |
Updated rotation | Changed the structure or participants in the team’s on-call rotation schedule. |
Updated routing rule | Edited the criteria or process for directing alerts or incidents to the team. |
Updated team alert policy | Changed the rules for managing or escalating alerts for the team. |
Updated team heartbeat | Modified the parameters or frequency of team system health checks |
Operations User Actions
Activity | Description |
|---|---|
Added alert notifications forwarding rule | Configured criteria to redirect alert notifications to specified channels or recipients for streamlined incident visibility |
Created alert notification rule | Established parameters for delivering alert notifications based on defined triggers and recipient preferences. |
Deleted alert notification rule | Removed a rule controlling how and when alert notifications are sent to users or groups |
Deleted alert notifications forwarding rule | Removed a configuration for redirecting alert notifications to external channels or recipients. |
Updated alert notification rule | Changed the triggers, delivery methods, or recipients for an existing alert notification rule. |
Updated alert notifications forwarding rule | Modified the criteria or destinations for forwarding alert notifications to ensure proper incident routing. |
Organizations
Activity | Description |
|---|---|
Viewed organization domains | Viewed the list of domains linked to the organization to confirm verified status, managed accounts coverage, and domain-based access controls. |
Viewed organization information | Viewed high-level organization details to review sites, apps, and administration settings. |
Viewed organization users | Viewed organization’s users under Directory. |
Portal-only customers
Activity | Description |
|---|---|
Updated customer account identity provider directory | Updated portal-only customer access restricted logins to Jira Service Management help centers and specific portals added for external customers seeking help. |
Products
Activity | Description |
|---|---|
Changed release track for product | Changed the release track configuration to control when the product receives changes and new features. |
Copied data to sandbox | Copied production environment data to the sandbox, replacing existing sandbox data with newly copied content. |
Created sandbox | Created a new sandbox within an existing sandbox site or in a new site. |
Deleted sandbox | Deleted a sandbox from the organization. |
Opted in to defer rollout for product | Enabled organization admins to defer the rollout of specific changes. |
Released bundle changes for product | Deployed a group of changes to the product on the scheduled cadence. |
Restored sandbox | Recovered a previously deleted sandbox. |
Rovo admin actions
Activity | Description |
|---|---|
Created 3P Connector connection | Established a new third-party connector connection to integrate external applications and streamline data exchange across your environment. |
Created Rovo bookmark | Added a new Rovo bookmark to provide quick access to frequently used resources within your workspace, following established configuration settings. |
Deleted 3P Connector connection | Disconnected an active third-party connector integration to cease data transfer and revoke associated permissions. |
Deleted Rovo bookmark | Deleted an existing Rovo bookmark from your environment to restrict access to specific resources for improved management. |
Updated 3P Connector connection | Changed the configuration or credentials of a third-party connector connection to ensure continued integration security and functionality. |
Updated Rovo bookmark | Modified the details or location of an existing Rovo bookmark to reflect revised access requirements or resource changes. |
Rovo MCP User Actions
Activity | Description |
|---|---|
Invoked tool | Triggered the execution of a designated tool to perform a specific action or workflow within the managed control panel environment. |
Rovo user actions
Activity | Description |
|---|---|
Create definition in Rovo | Added a new definition in Rovo to establish or refine operational parameters for user or system workflows. |
Created Rovo agent | Provisioned a Rovo agent to automate or facilitate process execution and user interactions within the managed environment. |
Deleted Rovo agent | Removed a Rovo agent to discontinue its automated process handling and associated actions within your environment. |
Started chat with Rovo agent | Initiated a direct conversation with a Rovo agent to request assistance or perform specific tasks through real-time interaction |
Updated Rovo agent | Changed configuration or properties of a Rovo agent to align with updated requirements or workflows. |
Security policies
Activity | Description |
|---|---|
Activated data security policy | Activated a data security policy to start enforcing controls on covered apps, projects, spaces, or classification levels. |
Added apps to data security policy | Added specific cloud apps to a data security policy so their content is governed by the policy’s controls. |
Added authentication policy | Added an authentication policy to manage single sign-on, two-step verification, and other security settings for a set of users. |
Added coverage for data security policy | Added new coverage, such as apps, specific projects, spaces, or classification levels to the data security policy. |
Added description for data security policy | Added or updated the policy description to document the purpose, scope, and usage of the data security policy. |
Added products to data security policy | Added Atlassian products to a data security policy to extend its coverage and apply the same data protection rules. |
Added rule to data security policy | Added a data security rule, such as blocking exports or public links, to control how covered content can be accessed or shared. |
Added SAML configuration | Added a SAML single sign-on configuration so that managed accounts can authenticate through an external identity provider. |
Archived classification level | Archived a classification level so that it’s no longer available for new content. |
Authentication policy type updated | Updated the authentication policy type or directory context, changing how the policy applies to managed accounts. |
Changed authentication policy for domain | Changed the authentication policy assigned to a verified domain, which may update authentication and security requirements for its users. |
Changed default authentication policy | Changed which authentication policy is the default for new or unassigned users in the selected directory. |
Changed user’s authentication policy | Changed the authentication policy associated with a specific user to adjust their authentication and security requirements. |
Created classification level | Created a classification level to label sensitive content across apps. |
Created data security policy | Created a data security policy to define coverage and rules that protect your organization’s cloud data. |
Deactivated data security policy | Deactivated a data security policy so its controls are no longer enforced on covered content. |
Deleted authentication policy | Deleted an authentication policy so it can no longer be enforced for any users. |
Deleted data security policy | Deleted a data security policy so that its rule no longer apply to the organization. |
Deleted SAML configuration | Deleted the SAML single sign-on configuration so that users can no longer authenticate through that identity provider. |
Enforced two-step verification for managed accounts | Enforced two-step verification for all managed accounts covered by the policy, requiring an additional verification step. |
Enforced two-step verification for user | Enforced two-step verification for a specific user, requiring an additional factor each time they sign in. |
Excluded user from two-step verification | Excluded a user from the policy’s two-step verification requirement so they can sign in without a second factor. |
External user types updated | Updated settings for external user types, adjusting how guests or collaborators can access products and data. |
Failed to update authentication policy for domain | Failed to update the authentication policy for a specified domain, leaving existing settings in place. |
Failed to update authentication policy for user | Failed to update the authentication policy for a specific user leaving existing settings in place. |
Published classification level | Published a classification level so users can start applying it to content. |
Removed apps from data security policy | Removed selected apps from a data security policy so their content is no longer covered by that policy. |
Removed coverage for data security policy | Removed existing coverage, such as apps, projects, spaces, or classification levels, from a data security policy. |
Removed domain from authentication policy | Removed a verified domain from an authentication policy so that users with that domain are no longer governed by that policy. |
Removed external user | Removed an external user from the organization or app access. |
Removed products from data security policy | Removed app from a data security policy so the policy no longer applies to their data. |
Removed rule from data security policy | Removed a rule from a data security policy, relaxing restrictions on covered content. |
Removed user from authentication policy | Removed a user from an authentication policy so they are no longer subject to that policy’s settings. |
Renamed classification level | Renamed a classification level to update how the label appears to users. |
Renamed data security policy | Renamed a data security policy to better reflect its purpose or scope. |
Reset password for user | Reset the password for a managed account, requiring the user to set a new password. |
Reset password for users in authentication policies | Reset passwords for all users covered by authentication policies, requiring them to choose new passwords. |
Reset passwords for managed accounts | Reset passwords for managed accounts, requiring them to set new passwords. |
Reset session for external users | Reset active sessions for external users, which logs them out and requires them to sign in. |
Reset session for users in authentication policies | Reset active sessions for users in authentication policies, which logs them out and requires them to sign in with updated controls. |
Reset two-step verification for user | Reset two-step verification for a user, which requires them to reconfigure their second factor the next time they log in. |
Restored classification level | Restored a previously archived classification level so it can be used again. |
Revoked API tokens for users in authentication policy | Revoked existing API tokens for users covered by an authentication policy. |
Saved external user | Saved changes to an external user’s details or access. |
Scheduled product move to realm | Scheduled a product’s data to move to a different realm to meet data residency requirements. |
Started storing user-created activity | Started storing user-created activity events to support monitoring and investigation in the organization audit log. |
Stopped enforcing two-step verification for managed account | Stopped enforcing two-step verification for a managed account so the user can sign in with only their primary credentials. |
Stopped storing user-created activity | Stopped storing user-created activity events, reducing the audit data retained for investigations. |
Switched app list rule on data security policy | Switched the app list rule on a data security policy, changing which apps are allowed or blocked under the policy. |
Updated authentication policy | Updated an authentication policy’s settings, such as single sign-on, two-step verification, password requirements, or session duration. |
Updated classification level | Updated a classification level, such as name, description, or availability for new content. |
Updated coverage from data security policy | Updated the data included in a policy’s coverage so that specific apps, projects, spaces, or classification levels are protected. |
Updated description for data security policy | Updated the description for a data security policy to clarify its intent and usage. |
Updated idle session duration | Updated the idle session timeout in an authentication policy, changing how long users stay signed in without activity. |
Updated password policy | Updated password policy settings, such as complexity or expiry requirements, for managed accounts. |
Updated SAML configuration | Updated the SAML single sign-on configuration, such as certificates or endpoints, for managed accounts. |
Validated organization policy | Validated a policy to confirm its configuration is complete and can be enforced. |
Viewed organization policies | Viewed the list of security policies, including their status and key settings. |
Service Account Actions
Activity | Description |
|---|---|
Created API token | Create an API token for a service account to authenticate access to Atlassian apps. |
Created service account | Created a service account to perform automated tasks and integrations without human intervention. |
Deleted service account | Deleted the service account and its associated credentials which blocks access to Atlassian apps. |
Revoked API token | Revoked an API token for the service account to block access to Atlassian apps. |
Updated service account | Updated service account details, such as name, description, or app permissions. |
Settings
Activity | Description |
|---|---|
Added domain to verify | Added domain to the organization to verify the domain. |
Added product to data retention | Added Atlassian cloud app to data retention policy to apply retention rules. |
Added user as organization admin | Assigned admin role to user to grant access to organization-wide security, billing, and user management settings |
API keys searched | Searched for admin API keys in the organization to review or filter keys by owner, status, or usage context. |
API tokens searched | Searched for user API tokens to review token status and troubleshoot access |
Claimed accounts for domain | Claimed accounts for a verified domain to become managed accounts in the organization. |
Confluence company-connection created | Created a Confluence company connection to link Confluence content. |
Confluence company-connection deleted | Deleted Confluence company connection to stop data. |
Created admin API key | Created an API key to enable access to organization-level administration APIs |
Created API token | Created a user API token to authenticate access to Atlassian apps |
Created application tunnel | Created an application tunnel to establish a secure, outbound-only connection. |
Created audit log webhook registration | Registered an audit log webhook to send audit log data to a third-party tool. |
Created identity provider directory | Created an identity provider directory to sync user accounts from your identity provider |
Deleted application tunnel | Deleted an application tunnel to terminate the connection between an Atlassian organization and data center |
Deleted audit log webhook registration | Deleted an audit log webhook to stop sending audit data a third-party tool. |
Deleted identity provider directory | Deleted an identity provider directory which means we no longer sync accounts from your identity provider to the Atlassian directory. |
Exported accounts for verified domain | Exported a CSV file of managed accounts to see details such as name, email, Atlassian ID, status, last active date, billable for Atlassian Guard, app access. |
Exported API keys | Exported a CSV file of API keys with details about date created, scopes, expiration date and date last used. |
Exported API tokens | Exported a CSV file with details about user API tokens such as date created, expiration date and date last used. |
Exported discovered products | Exported a CSV file of discovered Atlassian apps associated with this organization. |
Exported Enterprise product users | Exported a CSV file of Enterprise subscription usage. |
Exported external users | Exported a CSV file of external users to see details such as name, email, Atlassian ID, last active date, billable for Atlassian Guard, external user settings. |
Exported managed accounts | Exported a CSV file of managed accounts to see details such as name, email, Atlassian ID, status, last active date, billable for Atlassian Guard, app access |
Exported organization audit log | Exported a CSV of organization audit log events for historical analysis or ingestion into external logging tools. |
Exported user counts list | Exported user count data by app or directory to see subscription and usage information |
Initiated creation of site | Initiated creation of a site for one or more Atlassian apps in the organization. |
Initiated transfer of products from organization | Initiated transfer of selected apps from this organization to another organization from the current organization to a different organization. |
Initiated update to site URL | Initiated update to site URL. |
Linked domain to directory | Linked a domain to an identity provider to update account information and provision users to the linked domain |
Moved domain from directory | Moved a domain between directories to change which identity provider manages its accounts. |
New site created | Created Atlassian site and provisioned selected apps for the organization. |
Regenerated token for application tunnel | Regenerated the security key for an application tunnel to rotate credentials. |
Removed domain | Removed a domain from the organization which means you no longer manage the accounts associated with the domain |
Removed product from data retention | Removed an Atlassian from the organization’s data retention policy so its data no longer follows configured retention rules. |
Removed user as an organization admin | Removed organization admin role for user, revoking access to organization-level administration features. |
Renamed identity provider directory | Renamed identity provider directory with company naming conventions. |
Revoked admin API key | Revoked API key to block access to organization administration APIs. |
Revoked API token | Revoked user API token to block authentication to APIs |
Settings update | Updated one or more organization settings related to security, user management, or app configuration. |
Started to verify domain | Started domain verification by configuring either DNS or HTTPS records to manage accounts for the domain. |
Unclaimed accounts for domain | Unclaimed managed accounts for a domain to stop managing the accounts. |
Unverified domain | Removed verified domain to become an unverified domain, limiting its ability to manage accounts. |
Updated account profile for user | Updated profile details such as name, email alias, or identity directory attributes for a managed account. |
Updated audit log webhook registration | Updated settings for a registered audit log webhook. |
Updated automatic account claim | Updated automatic account claim settings that control how accounts become managed accounts |
Updated in-product recommendation preferences | Updated organization preferences for managed account app recommendations |
Updated login page | Updated organization login page configuration. |
Updated UGC use consent | Updated consent settings for how to improve Atlassian apps with user-generated content. |
Verified domain | Verified domain ownership to manage accounts and security for the domain in the organization |
Viewed API token | Viewed API token details, such as date created or expiration creation time, without updating the API token settings. |
Viewed discovered products | Viewed discovered Atlassian apps associated with domains to see the app footprint in the organization. |
Viewed discovered products count | Viewed aggregated counts of discovered apps to understand app usage from managed accounts and external users. |
Talent User Actions
Activity | Description |
|---|---|
All data removed | Removed all Talent data from the service to keep workspace clean. |
Created Talent custom field | Created a new Talent custom field by defining its name, field type, and description. |
Data imported | Imported Talent data to map fields and keep your data structured and consistent. |
Deleted Talent custom field | Deleted Talent custom field from your configuration so it no longer appears on projects, goals, or related requests. |
Updated Talent custom field | Updated Talent custom field by updating its name, description, or settings. |
Team Management
Activity | Description |
|---|---|
Added user to team | Added a user to the team, granting access based on the team’s permissions and configured roles. |
Archived team | Archived the team to keep work organized while retaining access to support resources and existing configurations for your sites and services. |
Changed assigned site for team | Changed the assigned site for the team so members can find answers, check system status, and access documentation tied to that specific site. |
Changed team description | Updated the team’s description to reflect new information, improving clarity for members and administrators. |
Changed team name | Modified the team’s name to align with current organizational standards or naming conventions. |
Changed team visibility from organization to site | Changed team visibility from the organization level to a specific site so team access and support resources are limited to that site. |
Changed team visibility from site to organization | Changed team visibility from a single site to the organization so members can view shared resources, billing information across sites. |
Changed to managed team | Converted the team to a managed status, enabling centralized administration and compliance control features. |
Changed to normal team | Converted the team to a standard configuration, removing managed status and associated administration controls. |
Created team | Created a new team to facilitate collaboration and manage access to projects and resources |
Deleted help pointer | Deleted a guidance link or help pointer previously available to team members for quick reference. |
Deleted kudos | Removed a kudos or recognition entry from the team’s activity feed. |
Deleted team | Permanently removed the team and its associations from the organization’s directory |
Linked team to Confluence space | Established a connection between the team and a Confluence space, enabling shared access and collaboration. |
Linked team to group | Associated the team with a user group to synchronize membership and permissions |
Linked team to Jira project | Connected the team to a Jira project, granting project access and aligning workflows. |
Linked team to Loom space | Linked the team to a Loom space, allowing members to access and share video resources |
Linked team to SCIM group | Synchronized the team with a SCIM group for automated user provisioning and management. |
Removed user from team | Removed a user from the team, revoking associated access and permissions |
Requested to join team | Submitted a request to join the team, pending approval from administrators or team owners |
Restored team | Reinstated a previously deleted team and its associations within the organization’s environment. |
Unarchived team | Unarchived the team to restore access to shared resources, support options, and configuration. |
Unlinked team from Confluence space | Disconnected the team from a Confluence space, revoking shared collaboration access. |
Unlinked team from group | Removed the association between the team and a user group, disabling synchronized membership and permissions. |
Unlinked team from Jira project | Disconnected the team from a Jira project, removing project access for team members |
Unlinked team from Loom space | Removed the link between the team and a Loom space, restricting access to shared video resources. |
Unlinked team from SCIM group | Disconnected the team from a SCIM group, halting automated provisioning and user synchronization. |
User-access settings
Activity | Description |
|---|---|
Added domain to approved domains | Added an email domain so users with matching addresses can get access to selected apps according to the approved domain configuration. |
Added notify admin setting | Updated notifications so admins receive emails when users request access or join an app. |
Added products to approved domains | Added apps to an approved domain so users from that domain receive predefined app access and roles when they request access or join. |
Added site based approved domains | Added approved domains scoped to a specific site so users from those domains can join apps on that site. |
Connected to third-party integrations | Connected the organization to an external identity or provisioning provider so users and groups can be synced and managed centrally. |
Created invitation URL | Generated an invitation link that can be shared so people can join an app without individual email invites. |
Disabled invites of managed accounts | Blocked invitations from being sent to managed accounts so access for those users must be controlled through centralized user management. |
Disabled third-party invites | Prevented users from inviting others through connected third-party systems so invitations occur only through Atlassian-managed flows. |
Disconnected from third-party integrations | Removed the connection to an external identity or provisioning provider so new syncs and updates from that system stop. |
Enabled invites of managed accounts | Allowed invitations to be sent to managed accounts so admins can grant app access directly to users on verified domains. |
Enabled third-party invites | Allowed users to invite others through connected third-party systems so external tools can provision or request access to apps. |
Regenerated invitation URL | Invalidated the existing invitation link and created a new one so only the latest URL can be used to join. |
Remove domain from approved domains | Removed an email domain so users from that domain no longer get automatic app access. |
Removed invitation URL | Turned off the invitation link so it can no longer be used to join the app or site. |
Removed products from approved domains | Removed apps from an approved domain so users from that domain stop receiving request acces or join. |
Removed site based approved domains | Cleared site-scoped approved domains so users from those domains no longer automatically join apps on that site. |
Reset user access settings | Restored app access and invite controls to their default configuration to reset how users get access. |
Updated access request settings | Changed how users can request access to apps, including whether requests are allowed and how they are reviewed by admins. |
Updated approved domains through domains enabled signup promotion | Modified approved domains when enabling sign-up via email domains so eligible users can join apps without manual invites. |
Updated invite settings | Adjusted who can send invitations and which domains or users they can invite to apps in the organization. |
Updated not allowed invite note | Edited the message shown to users when they try to invite others but invitations are disabled for that app. |
Updated notify admin settings | Changed which admin notifications are sent when users request or gain access so the right admins stay informed. |
Updated site based domain enabled signup setting | Changed site-level domain sign-up controls so only users from specified domains can self-join apps on that site. |
User management
Activity | Description |
|---|---|
Added admin by Atlassian support | Granted an admin role to a user after Atlassian Support verified a request to update their role in Atlassian Administration. |
Added user to group | Added a user to a group, assigning the user any app roles and admin roles granted by the group. |
Admin group search within organization | Searched for groups that grant an admin role in an organization. |
Admin users search within organization | Searched for users that have an admin role in an organization. |
Approved access request | Approved a pending app access request, provisioning the user (if applicable) and granting app access. |
Created access request | Requested access to an app that requires admin approval. |
Created account for user | Created an Atlassian account for a user. |
Created group | Created a new group in a directory. |
Deleted group | Delete a group in a directory, removing any app roles or admin roles from users that were granted by the group. |
Exported users from directory | Exported a list of users and their app access in the organization directory (centralized user management experience only). |
Exported users from site | Exported a list of users and their app access in a site directory (original user management experience only). |
Granted organization access to user | Added a user to an organization directory (centralized user management experience only). |
Granted product access to group | Assigned app access to a group, giving its users app access to an app. |
Granted product access to user | Assigned an app role to grant app access to a user. |
Granted product admin access to group | Assigned an app admin role to a group, giving its users the app admin role for an app. |
Granted role to group | Assigned a role to a group, giving its users the same role. |
Granted role to user for product | Assigned an app role to a user. |
Granted site access to user | Added a user to a site directory, enabling app access in the site if assigned (original user management experience only). |
Invited user to organization | Invited a user to an organization directory (centralized user management experience only). |
Invited user to site | Invited a user to a site directory (original user management experience only). |
Joined through approved domains | Gained access to an app as a result of the organization’s approved domains settings. |
Joined through invitation URL | Gained access to an app through an invitation link. |
Logged in as user | Initiated a temporary session as the user to validate permissions and troubleshoot access. |
Made group a default group | Set a group as a default group for a role. |
Product role migration | Updated users and groups to new app role mappings to align with current roles. |
Rejected access request | Denied a pending app access request. |
Remove default access from group | Removed a group as a default group for a role. |
Removed admin by Atlassian support | Removed an admin role from a user after Atlassian Support verified a request to remove their role in Atlassian Administration. |
Removed default setting from group | Removed a group as a default group for a role. |
Removed product access from group | Removed app access from a group, removing the app access from users in the group, unless granted elsewhere. |
Removed role from group | Removed a role from a group, removing the role from users in the group, unless granted elsewhere. |
Removed user from group | Removed a user from a group, removing any app roles and admin roles granted by the group from the user. |
Removed user from organization | Removed a user from an organization directory (centralized user management experience only). |
Removed user from site | Removed a user from a site directory (original user management experience only). |
Renamed a group | Updated the name of a group. |
Renamed duplicate group | Renamed a group to resolve a duplicate name conflict. |
Resent invite to user | Resent an invitation to a user to join an app in an organization (centralized user management experience only). |
Resent site invitation to user | Resent an invitation to a user to join an app in a site (original user management experience only). |
Reuse site group name | Reassigned a previously used site group name after resolving conflicts or deletions. |
Revoked organization access from user | Removed a user from an organization directory (centralized user management experience only). |
Revoked product access from user | Removed an app role that granted app access to a user. |
Revoked role from user for product | Removed an app role from a user. |
Revoked site access from user | Removed a user from a site directory (original user management experience only). |
Viewed last active dates | Viewed the last active date of users using an API. |
User provisioning
Activity | Description |
|---|---|
Added group from identity provider | Added synced group from the identity provider directory into a group to grant app access. |
Added SCIM configuration for portal-only customers | Added SCIM configuration to connect an identity provider and sync portal-only customers between your external directory and Jira Service Management using SCIM provisioning. |
Added SCIM configuration settings for portal-only customers | Added SCIM configuration settings to enable provisioning and syncing portal-only customers from your identity provider directory. |
Added user from identity provider | Added synced user account from the identity provider directory into a group to grant app access. |
Added user to group | Added a user to a synced group so their access to associated apps and sites matches group-based permissions. |
Cleared user provisioning troubleshooting log | Cleared stored user provisioning troubleshooting log to reset monitoring for future sync activity. |
Completed automatic sync from external directory | Completed scheduled syncing from identity provider to update users, groups, and memberships in the organization. |
Completed manual sync from external directory | Completed manual sync to organization from identity provider to update users, groups, and memberships. |
Connected to Google workspace | Connected Google Workspace to the organization to provision users and groups automatically. |
Created user provisioning directory | Created an identity provider directory in the organization to sync users users and groups from the identity provider. |
Deleted SCIM configuration for portal-only customers | Deleted the SCIM configuration that connected your identity provider to Jira Service Management, stopping SCIM provisioning for portal-only customers in that directory. |
Deleted SCIM configuration settings for portal-only customers | Deleted stored SCIM configuration settings, including the SCIM base URL and API key, to remove provisioning and syncing of portal-only customers from your identity provider. |
Deleted user provisioning directory | Deleted identity provider directory from the organization, which stops user and group syncing |
Disabled requiring Google login | Disabled the requirement for users to authenticate with Google. |
Disabled sync from external directory | Disabled syncing from the identity provider to stop user and group updates to the organization. |
Disconnected from Google workspace | Disconnected from Google Workspace to longer sync user and group updates. |
Enabled requiring Google login | Enabled the requirement for users to log in with Google when accessing Atlassian apps. |
Enabled sync from external directory | Enabled users and groups to sync from the identity provider to the organization. |
Initiated automatic sync from external directory | Initiated an automatic sync from the identity provider to update users, groups, and memberships. |
Initiated manual sync from external directory | Initiated a manual sync from the identity provider to update users, groups, and memberships. |
Invited user after Google workspace sync | Invited a provisioned Google Workspace user to complete account setup and access Atlassian apps. |
Linked Atlassian account to user in identity provider | Linked an existing Atlassian account to a matching user record in the identity provider. |
Made user a managed account | Claimed a managed account to manage its profile and app access. |
Made user an unmanaged account | Unclaimed a managed account to stop managing the users profile and app access. |
Reconfigured external directory | Reconfigured SCIM configuration settings such as base URL, credentials, or attribute mappings. |
Regenerated API key for SCIM directory | Regenerated the SCIM API key to maintain secure connectivity with the identity provider. |
Regenerated SCIM provisioning API key for portal-only customers | Regenerated the SCIM provisioning API key for the identity provider directory used to sync portal-only customers, updating the credential used by your external directory. |
Removed group from identity provider | Removed a group from the identity provider so it no longer appears in the organization or have app access. |
Removed user from group | Removed a synced user from a group, revoking app access granted by the group. |
Removed user from identity provider | Removed a user from the identity provider so the account no longer appears in the organization or has app access. |
Removed user provisioning directory | Removed the identity provider directory from the organization, including its ability to sync users and groups. |
Renamed a group | Renamed a synced group in the organization. |
Synced all groups with conflicts from external directory | Synced groups with the same name to resolve groups name conflicts. |
Synced groups to site | Synced groups from the organization directory to a specific site for app access and permissions. |
Synced groups with conflicts from external directory | Resolved group conflicts by syncing group and users in your organization to match the group and users in your identity provider. |
Synced user to site | Synced a user from the organization to a specific site, enabling assignment to apps through groups. |
Unliked group from SCIM | Unlinked a synced group to stop group updates from the identity provider. |
Unlinked Atlassian account from user in identity provider | Unlinked an Atlassian account from the identity provider to stop syncing user updates in the organization. |
Updated account profile for user | Updated managed account profile attributes, such as name or email in the identity provider. |
Updated external identifier of group | Updated the external identifier for a synced group to match the group name in the identity provider. |
Updated Google workspace invite message | Updated the invite message sent to Google Workspace users when invited to Atlassian apps. |
Updated SCIM configuration settings for portal-only customers | Updated SCIM configuration settings for portal-only customers to change how your identity provider provisions and syncs users and groups to Jira Service Management. |
Updated user identifier to email for identity provider | Updated the user identifier setting as email address to match with the identity provider identifier for an Atlassian account. |
Updated user identifier to user principal name for identity provider | Updated the user identifier setting as user principal name (UPN) to match with the identity provider identifier for an Atlassian account. |
Was this helpful?