We are excited to share that Confluence Cloud will now be syncing data for teams, in addition to users and groups, into the Confluence database.
This update will include a one-time sync of all existing teams data as well as subsequent syncs for any new teams data moving forward. As always, each sync will generate records in the audit logs detailing what data changed within your instance.
Please note that this change does not yet allow teams to be used in any Confluence features, and therefore should have no noticeable impact on users.
Why we’re making this change
As previously announced, we will be introducing teams to Confluence Permissions. This change is a prerequisite for this feature.
What’s changing
Whenever changes are made to a group today (e.g. a new group is created, membership for an existing group changes, the group’s name is updated, etc.), those changes are synced into the Confluence database from Atlassian Administration. When this sync occurs, Confluence generates audit logs summarizing all the changes that were processed for app admins to view and fires webhooks for third-party apps to asynchronously process as well.
We will now be extending this functionality to support teams in the same we support groups today.
Example Audit Logs for Teams Changes
How teams are represented in Confluence
Teams are represented the same way as groups in Confluence. However, we are introducing two new fields to groups that will help determine which collections of users are used as teams vs. groups.
-
usageType(String)-
Default Value:
USERBASE_GROUP -
Valid Values:
-
USERBASE_GROUP: This value indicates that the collection of users is used as a group. -
TEAM_COLLABORATION: This value indicates that the collection of users is used as a team.
-
-
-
managedBy(String)-
Default Value:
ADMINS -
Valid Values:
-
ADMINS: This value indicates that the collection of users is managed by org, site or product admins. -
EXTERNAL: This value indicates that the collection of users is managed externally (through SCIM, HRIS, etc.). -
TEAM_MEMBERS: This value indicates that the collection of users is managed by its members, who aren’t necessarily admin users. -
OPEN: This value indicates that the collection of users is not actively managed by any users.
-
-
How to programmatically look up a Team that has been synced into your Confluence instance
As mentioned above, group-based webhooks will now be supporting teams. You can reference our existing V1 REST API for Groups to look up any team by ID in Confluence. However, please note that no mutation APIs will be supporting teams until we release official support for Teams in Confluence.
More information about the Group API can be found on our public developer documentation site: https://developer.atlassian.com/cloud/confluence/rest/v1/api-group-group/#api-wiki-rest-api-group-by-id-get.
If you have any questions or concerns, please leave us a comment in the section below. Thank you!