Disable Team Application
Removes a team's entitlement to an application, revoking team-derived access for its members. Requires team owner.
Required scopes: auth:teams:manage or auth:teams:manage:app (the latter additionally requires the team to be entitled to the calling application)
JWT access token obtained via OAuth2 flow or service account
In: header
Header Parameters
Define the version of the Connect protocol
1Define the timeout, in ms
Request Body
application/json
1 <= length <= 128length <= 64Response Body
application/json
application/json
curl -X POST "https://auth.xeonr.io/xeonr.auth.api.v1.TeamsService/DisableTeamApplication" \ -H "Connect-Protocol-Version: 1" \ -H "Content-Type: application/json" \ -d '{}'{}{
"code": "not_found",
"message": "string",
"details": [
{
"type": "string",
"value": "string",
"debug": {}
}
]
}Describe Team Membership POST
Authoritatively answers whether a subject is a member of a team, with their team role and per-application role names for the calling application. This is the product-side authorisation check for destructive or sensitive operations where a cached token claim is not fresh enough. **Required scopes:** `auth:teams:read`
Enable Team Application POST
Entitles a team to an application. Only applications with automatic team binding enabled may be self-served; others require an organisation administrator. Requires team owner. Under `auth:teams:manage:app` a product may entitle ONLY itself, and only to a team the calling user owns and names explicitly; a team the caller does not own is indistinguishable from one that does not exist. Naming another application under that scope is refused. **Required scopes:** `auth:teams:manage` or `auth:teams:manage:app`