Skip to content

Atlassian: Create permission grant

Atlassian permissionSchemes.createPermissionGrant: arguments, response, policy and SDK examples.

← Permission schemes operations · Get started

Operation atlassian.createpermissiongrant

Provider route: POST /{cloudId}/rest/api/3/permissionscheme/{schemeId}/permission. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/atlassian with npm, or alter-sdk-atlassian with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { AtlassianIntegration } from "@alter-ai/atlassian";
async function execute(input: Parameters<AtlassianIntegration["permissionSchemes"]["createPermissionGrant"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new AtlassianIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.permissionSchemes.createPermissionGrant(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_atlassian import AtlassianIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = AtlassianIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.permission_schemes.create_permission_grant(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
pathobjectRequired within parentAdditional keys: not allowed
path.cloudIdstringRequired within parentPattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
path.schemeIdintegerRequired within parentFormat: int64
queryobjectOptionalAdditional keys: not allowed
query.expandstringOptional
bodyModelRequired within parentExpand Create permission grant — request body — body

Referenced models: Create permission grant — request body — body

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand Create permission grant — response body

Referenced models: Create permission grant — response body

Create permission grant — response body
FieldTypePresenceDescription and constraints
$objectRootDetails about a permission granted to a user or group.
Additional keys: allowed
holderJSONOptional
holder (anyOf 1)ModelAlternativeExpand Create permission grant — response body — holder expand, parameter, type, value
The user or group being granted the permission. It consists of a `type`, a type-dependent `parameter` and a type-dependent `value`. See [Holder object](../api-group-permission-schemes/#holder-object) in *Get all permission schemes* for more information.
holder (anyOf 2)nullAlternative
idJSONOptional
id (anyOf 1)JSONAlternative
id (anyOf 1) (anyOf 1)integerAlternativeThe ID of the permission granted details.
Format: int64
Read only: true
id (anyOf 1) (anyOf 2)stringAlternativePattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
id (anyOf 2)nullAlternative
permissionJSONOptional
permission (anyOf 1)stringAlternativeThe permission to grant. This permission can be one of the built-in permissions or a custom permission added by an app. See [Built-in permissions](../api-group-permission-schemes/#built-in-permissions) in *Get all permission schemes* for more information about the built-in permissions. See the [project permission](https://developer.atlassian.com/cloud/jira/platform/modules/project-permission/) and [global permission](https://developer.atlassian.com/cloud/jira/platform/modules/global-permission/) module documentation for more information about custom permissions.
permission (anyOf 2)nullAlternative
selfJSONOptional
self (anyOf 1)stringAlternativeThe URL of the permission granted details.
Format: uri
Read only: true
self (anyOf 2)nullAlternative

Referenced models: Create permission grant — response body — holder expand, parameter, type, value

Create permission grant — request body — body
FieldTypePresenceDescription and constraints
$objectRootDetails about a permission granted to a user or group.
Additional keys: allowed
holderModelOptionalExpand Create permission grant — request body — body holder
The user or group being granted the permission. It consists of a `type`, a type-dependent `parameter` and a type-dependent `value`. See [Holder object](../api-group-permission-schemes/#holder-object) in *Get all permission schemes* for more information.
idintegerOptionalThe ID of the permission granted details.
Format: int64
Read only: true
permissionstringOptionalThe permission to grant. This permission can be one of the built-in permissions or a custom permission added by an app. See [Built-in permissions](../api-group-permission-schemes/#built-in-permissions) in *Get all permission schemes* for more information about the built-in permissions. See the [project permission](https://developer.atlassian.com/cloud/jira/platform/modules/project-permission/) and [global permission](https://developer.atlassian.com/cloud/jira/platform/modules/global-permission/) module documentation for more information about custom permissions.
selfstringOptionalThe URL of the permission granted details.
Format: uri
Read only: true

Referenced models: Create permission grant — request body — body holder

Create permission grant — response body — holder expand, parameter, type, value
FieldTypePresenceDescription and constraints
$objectRootDetails of a user, group, field, or project role that holds a permission. See [Holder object](../api-group-permission-schemes/#holder-object) in *Get all permission schemes* for more information.
expandJSONOptional
expand (anyOf 1)stringAlternativeExpand options that include additional permission holder details in the response.
Read only: true
expand (anyOf 2)nullAlternative
parameterJSONOptional
parameter (anyOf 1)stringAlternativeAs a group's name can change, use of `value` is recommended. The identifier associated withthe `type` value that defines the holder of the permission.
parameter (anyOf 2)nullAlternative
typeJSONOptional
type (anyOf 1)stringAlternativeThe type of permission holder.
type (anyOf 2)nullAlternative
valueJSONOptional
value (anyOf 1)stringAlternativeThe identifier associated with the `type` value that defines the holder of the permission.
value (anyOf 2)nullAlternative
Create permission grant — request body — body holder
FieldTypePresenceDescription and constraints
$objectRootDetails of a user, group, field, or project role that holds a permission. See [Holder object](../api-group-permission-schemes/#holder-object) in *Get all permission schemes* for more information.
Additional keys: not allowed
expandstringOptionalExpand options that include additional permission holder details in the response.
Read only: true
parameterstringOptionalAs a group's name can change, use of `value` is recommended. The identifier associated withthe `type` value that defines the holder of the permission.
typestringRequired within parentThe type of permission holder.
valuestringOptionalThe identifier associated with the `type` value that defines the holder of the permission.

SDK function policy ID: atlassian.createpermissiongrant. Catalog operation: createpermissiongrant. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["manage:jira-configuration"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.