# App Roles Returns all application roles. In Jira, application roles are managed using the Application access configuration page - https://support.atlassian.com/user-management/docs/give-users-access-to-products **Sync Type: Full Synchronisation** ## Requirements Before you connect Monad to Jira, you need an API token, email, and a domain: 1. Log in to https://id.atlassian.com/manage-profile/security/api-tokens. 2. Select Create API token. 3. Give your API token a name that describes what it does. 4. Select an expiration date for the API token. 5. Token expiration is 1 to 365 days* 6. Select Create. 7. Select Copy to clipboard, then paste the token to your script, or save it somewhere safe. 8. Your domain name is the unique subdomain of your Jira instance. If your Jira URL is 'acme.atlassian.net', then 'acme' is the domain name. 9. The email address is the one associated with your Atlassian account used to access Jira. ***Note:** When generating an API Token, please be mindful of its expiry date, as the token and its expiry is not generated by Monad. If the token expires, any inputs relying on it will result in errors. To continue, you will need to regenerate a new API Token through the UI. ## Details Monad uses the `cron` field to schedule the input at specific intervals, returning all users, including active users, inactive users and previously deleted users that have an Atlassian account. A full data sync is performed each time. ## Configuration The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below. #### Settings | Setting | Type | Required | Description | |---------|------|----------|-------------| | Email | string | Yes | The email address associated with your Atlassian account used to access Jira. | | Domain | string | Yes | This is the unique subdomain of your Jira instance. If your Jira URL is 'acme.atlassian.net', then 'acme' is the domain name. | | Cron | string | Yes | Cron expression for scheduling the input. | | API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. | #### Secrets | Secret | Type | Required | Description | |---------|------|----------|-------------| | Api Token | string | Yes | This is the token you generate from your Atlassian account for API access. | ## Related Articles - [https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about](https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about) - [https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-application-roles#api-group-application-roles](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-application-roles#api-group-application-roles) ## Sample Record ```json { "defaultGroups": [ "jira-core-users" ], "defaultGroupsDetails": [ { "groupId": "ab285aec-1d62-c823-179e-6bbfe609b10d", "name": "jira-core-users", "self": "https://enterprise.atlassian.net/rest/api/3/group?groupId=e0e35311-9563-e935-0112-89719f4ae73a" } ], "defined": false, "groupDetails": [ { "groupId": "3bbd00e9-3f10-3047-a32c-769805b260e3", "name": "jira-admins", "self": "https://enterprise.atlassian.net/rest/api/3/group?groupId=e64059f2-4d15-f858-3ea0-86e3ca4ea898" }, { "groupId": "2d529bc0-1da4-3a78-fb53-e23128e63522", "name": "jira-software-users", "self": "https://enterprise.atlassian.net/rest/api/3/group?groupId=539a4b2f-7272-0169-e4b1-d2fe946bde43" } ], "groups": [ "jira-core-users", "jira-testers" ], "hasUnlimitedSeats": false, "key": "bitbucket", "name": "Jira Core", "numberOfSeats": 15, "platform": false, "remainingSeats": 39, "selectedByDefault": false, "userCount": 5, "userCountDescription": "9 team members" } ```