@resolution/organizations-api-client 0.15.8 → 0.15.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (31) hide show
  1. package/lib/openapi/organizations/BaseOrganizationsApiClient.d.ts +5 -5
  2. package/lib/openapi/organizations/BaseOrganizationsApiClient.js +15 -1
  3. package/lib/openapi/organizations/BaseOrganizationsApiClient.js.map +1 -1
  4. package/lib/openapi/organizations/models/common.d.ts +39 -4
  5. package/lib/openapi/organizations/models/common.js +6 -2
  6. package/lib/openapi/organizations/models/common.js.map +1 -1
  7. package/lib/openapi/organizations/models/directory.d.ts +0 -203
  8. package/lib/openapi/organizations/models/directory.js +0 -59
  9. package/lib/openapi/organizations/models/directory.js.map +1 -1
  10. package/lib/openapi/organizations/models/groups.d.ts +68 -5
  11. package/lib/openapi/organizations/models/groups.js +18 -1
  12. package/lib/openapi/organizations/models/groups.js.map +1 -1
  13. package/lib/openapi/organizations/models/users.d.ts +337 -5
  14. package/lib/openapi/organizations/models/users.js +87 -2
  15. package/lib/openapi/organizations/models/users.js.map +1 -1
  16. package/lib/openapi/organizations/services/DirectoryService.d.ts +3 -607
  17. package/lib/openapi/organizations/services/DirectoryService.js +0 -550
  18. package/lib/openapi/organizations/services/DirectoryService.js.map +1 -1
  19. package/lib/openapi/organizations/services/DomainsService.d.ts +4 -4
  20. package/lib/openapi/organizations/services/EventsService.d.ts +8 -8
  21. package/lib/openapi/organizations/services/GroupsService.d.ts +605 -17
  22. package/lib/openapi/organizations/services/GroupsService.js +466 -0
  23. package/lib/openapi/organizations/services/GroupsService.js.map +1 -1
  24. package/lib/openapi/organizations/services/OrgsService.d.ts +2 -2
  25. package/lib/openapi/organizations/services/PoliciesService.d.ts +18 -18
  26. package/lib/openapi/organizations/services/UsersService.d.ts +542 -26
  27. package/lib/openapi/organizations/services/UsersService.js +488 -8
  28. package/lib/openapi/organizations/services/UsersService.js.map +1 -1
  29. package/lib/openapi/organizations/services/ValidateService.d.ts +2 -2
  30. package/lib/openapi/organizations/services/WorkspacesService.d.ts +2 -2
  31. package/package.json +3 -3
@@ -1,5 +1,6 @@
1
+ import * as commonHttpClient from "../../core/CommonHttpClient";
1
2
  import { CommonHttpService } from "../../core/CommonHttpService";
2
- import { type UserPage, type UsersSearchRequest, type UsersSearchPage, type MultiDirectoryUserPage, type MultiDirectoryUserRoleAssignmentPage, type MultiDirectoryUserStats } from "../models/users";
3
+ import { type UserProductAccessActivityPage, type UserPage, type OrganizationLevelRoleApiRequest, type RoleApiRequest, type InviteApiRequest, type UsersSearchRequest, type UsersSearchPage, type MultiDirectoryUserPage, type MultiDirectoryUserRoleAssignmentPage, type MultiDirectoryUserStats, type MultidirectoryInviteApiRequest, type MultidirectoryInviteSuccessResponse } from "../models/users";
3
4
  /**
4
5
  * Orgs Users APIs
5
6
  *
@@ -8,17 +9,127 @@ import { type UserPage, type UsersSearchRequest, type UsersSearchPage, type Mult
8
9
  */
9
10
  export declare class UsersService extends CommonHttpService {
10
11
  /**
11
- * Returns a page of users in an organization that match the supplied parameters.
12
+ * **The API is available for customers using the [new user management experience
13
+ * only](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592)**.
12
14
  *
13
- * @returns Returned if the request is successful.
15
+ * This API can be used to grant Platform Roles to a user.
16
+ *
17
+ * @path POST `/v1/orgs/{orgId}/users/{userId}/roles/assign`
18
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-users-userid-roles-assign-post
19
+ * @param params
20
+ */
21
+ assignRole: ({ orgId, userId, roleApiRequest }: {
22
+ /**
23
+ * Your organization has a unique ID. Find this ID in your Atlassian
24
+ * Administration URL or when you create your API key.
25
+ */
26
+ orgId: string;
27
+ /**
28
+ * The UserId on which the action(Role Assign) needs to happen. Use the [Search
29
+ * for users within an organization
30
+ * API](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v1-orgs-orgid-users-get)
31
+ * to get the userId.
32
+ */
33
+ userId: string;
34
+ roleApiRequest: RoleApiRequest;
35
+ }) => Promise<void>;
36
+ /**
37
+ * **This API is deprecated and will no longer work after June 30, 2026.** Use the
38
+ * [Remove user from directory
39
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-accountid-delete)
40
+ * instead.
41
+ *
42
+ * **The API is available for customers using the new user management experience
43
+ * only.** Learn more about the [new user management
44
+ * experience](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592).
45
+ *
46
+ * Specifications:
47
+ * - Remove user access to products listed in Atlassian Administration.
48
+ * - Remove users from **Users** and **Groups** in **Directory**.
49
+ * - Make product licenses available for active users.
50
+ *
51
+ * The users are not removed immediately; instead, they are placed in a queue for
52
+ * deletion. Please note that it may take some time for all users to be completely
53
+ * removed.
54
+ *
55
+ * Users with emails whose domain is claimed can still be found in **Managed
56
+ * accounts** in **Directory**.
57
+ *
58
+ * Learn the fastest way to call the API with a detailed
59
+ * [tutorial](https://developer.atlassian.com/cloud/admin/organization/remove-user/).
60
+ *
61
+ * @deprecated
62
+ * @path DELETE `/v1/orgs/{orgId}/directory/users/{accountId}`
63
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-directory-users-accountid-delete
64
+ * @param params
65
+ */
66
+ deleteV1OrgsOrgIdDirectoryUsersAccountId: ({ orgId, accountId }: {
67
+ /**
68
+ * Your organization has a unique ID. Find this ID in your Atlassian
69
+ * Administration URL or when you create your API key.
70
+ */
71
+ orgId: string;
72
+ /**
73
+ * Unique ID of the user's account that you are deleting.
74
+ * Use the [Jira User Search
75
+ * API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get)
76
+ * to get the accountId (if Jira is available for your Organization). **Jira APIs
77
+ * use a different [authentication method
78
+ * ](https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/).**
79
+ * If you don’t have Jira, export a .csv of the user list. Learn how to [export
80
+ * users from a
81
+ * site](https://support.atlassian.com/organization-administration/docs/export-users-from-a-site/).
82
+ */
83
+ accountId: string;
84
+ }) => Promise<void>;
85
+ /**
86
+ * Remove a user from a directory if you don’t want them to appear in your
87
+ * directory or have access to your apps anymore. You’re not billed for a user
88
+ * once they’re removed.
89
+ * You must invite the user to your organization again if you want to reinstate
90
+ * their access to your apps. You’ll need to assign their roles and group
91
+ * memberships again.
92
+ *
93
+ * @path DELETE `/v2/orgs/{orgId}/directories/{directoryId}/users/{accountId}`
94
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-accountid-delete
95
+ * @param params
96
+ */
97
+ deleteV2OrgsOrgIdDirectoriesDirectoryIdUsersAccountId: ({ orgId, directoryId, accountId }: {
98
+ /**
99
+ * Your organization has a unique ID. Find this ID in your Atlassian
100
+ * Administration URL or when you create your API key.
101
+ */
102
+ orgId: string;
103
+ /**
104
+ * A directory has a unique ID. Use the [Get directories
105
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v2-orgs-orgid-directories-get)
106
+ * to find the directory ID.
107
+ */
108
+ directoryId: string;
109
+ /**
110
+ * Every user has a unique ID. Find a user’s account ID by using the [Get users
111
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get).
112
+ */
113
+ accountId: string;
114
+ }) => Promise<void>;
115
+ /**
116
+ * Return a page of users in your organization that match the supplied parameters.
117
+ * By default, users in all your directories and all your managed accounts are
118
+ * returned (including managed accounts that aren’t in a directory).
119
+ *
120
+ * To get users in a directory only, use the `directoryIds` field. To get your
121
+ * managed accounts, regardless if they’re in a directory or not, use the
122
+ * `claimStatus` field.
123
+ *
124
+ * @returns Success
14
125
  * @path GET `/v2/orgs/{orgId}/directories/{directoryId}/users`
15
126
  * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-get
16
127
  * @param params
17
128
  */
18
- getDirectoryUsers: ({ orgId, directoryId, cursor, limit, accountIds, directoryIds, resourceIds, groupIds, claimStatus, status, accountStatus, membershipStatus, roleIds, searchTerm, sortBy }: {
129
+ getDirectoryUsers: ({ orgId, directoryId, cursor, limit, accountIds, directoryIds, resourceIds, groupIds, mfaEnabled, claimStatus, status, accountStatus, membershipStatus, roleIds, emailDomains, searchTerm, sortBy }: {
19
130
  /**
20
- * Your organization is identified by a Unique ID. You get your organization ID
21
- * and Organization API key simultaneously.
131
+ * Your organization has a unique ID. Find this ID in your Atlassian
132
+ * Administration URL or when you create your API key.
22
133
  */
23
134
  orgId: string;
24
135
  /**
@@ -61,6 +172,13 @@ export declare class UsersService extends CommonHttpService {
61
172
  resourceIds?: string[] | undefined;
62
173
  /** A list of group IDs. */
63
174
  groupIds?: string[] | undefined;
175
+ /**
176
+ * Whether or not a managed account has two-step verification enabled on their
177
+ * account. If `true`, they have two-step verification enabled.
178
+ * By default, all accounts are returned, regardless of two-step verification
179
+ * status.
180
+ */
181
+ mfaEnabled?: boolean | undefined;
64
182
  /**
65
183
  * The claim status for the user account. By default, both `managed` and
66
184
  * `unmanaged` accounts are returned.
@@ -78,8 +196,10 @@ export declare class UsersService extends CommonHttpService {
78
196
  * - `not_invited` - `accountStatus` is `active` and `membershipStatus` is
79
197
  * `no_membership`.
80
198
  * - `deactivated` - `accountStatus` is `inactive`.
199
+ * - `for_deletion` - Indicates whether or not a managed account is scheduled
200
+ * for deletion.
81
201
  */
82
- status?: ("active" | "suspended" | "not_invited" | "deactivated")[] | undefined;
202
+ status?: ("active" | "suspended" | "not_invited" | "deactivated" | "for_deletion")[] | undefined;
83
203
  /**
84
204
  * The lifecycle status of the account.
85
205
  * - `active` - The account is active and can be used.
@@ -124,7 +244,13 @@ export declare class UsersService extends CommonHttpService {
124
244
  * - `atlassian/ai-access` - Can use AI features in AI-enabled apps they have
125
245
  * access to.
126
246
  */
127
- roleIds?: ("atlassian/user" | "atlassian/user-access-admin" | "atlassian/admin" | "atlassian/guest" | "atlassian/contributor" | "atlassian/customer" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/site-admin" | "atlassian/org-admin" | "atlassian/ai-access")[] | undefined;
247
+ roleIds?: ("atlassian/user" | "atlassian/admin" | "atlassian/guest" | "atlassian/customer" | "atlassian/contributor" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/org-admin" | "atlassian/site-admin" | "atlassian/user-access-admin" | "atlassian/ai-access")[] | undefined;
248
+ /**
249
+ * The email domain to filter the results. The email domain will be used to search
250
+ * against the account email domain. For example, get all users with the
251
+ * `@atlassian.com` or `@example.com` email domain.
252
+ */
253
+ emailDomains?: string[] | undefined;
128
254
  /** A search term to search the `nickname` and `email` fields. */
129
255
  searchTerm?: string | undefined;
130
256
  /**
@@ -133,7 +259,7 @@ export declare class UsersService extends CommonHttpService {
133
259
  */
134
260
  sortBy?: ({
135
261
  /** The name of the field to sort the results by. */
136
- field: "nick_name" | "email";
262
+ field: "nick_name";
137
263
  /** The direction to sort the results by. */
138
264
  direction: "asc" | "desc";
139
265
  } & {
@@ -142,16 +268,22 @@ export declare class UsersService extends CommonHttpService {
142
268
  }) => Promise<MultiDirectoryUserPage>;
143
269
  /**
144
270
  * Returns a count of users in an organization that match the supplied parameters.
271
+ * By default, users in all your directories and all your managed accounts are
272
+ * counted (including managed accounts that aren’t in a directory).
145
273
  *
146
- * @returns Returned if the request is successful.
274
+ * To count users in a directory only, use the `directoryIds` field. To count your
275
+ * managed accounts, regardless if they’re in a directory or not, use the
276
+ * `claimStatus` field.
277
+ *
278
+ * @returns Success
147
279
  * @path GET `/v2/orgs/{orgId}/directories/{directoryId}/users/count`
148
280
  * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-count-get
149
281
  * @param params
150
282
  */
151
- getDirectoryUsersCount: ({ orgId, directoryId, accountIds, directoryIds, resourceIds, groupIds, claimStatus, status, accountStatus, membershipStatus, roleIds, searchTerm }: {
283
+ getDirectoryUsersCount: ({ orgId, directoryId, accountIds, directoryIds, resourceIds, groupIds, mfaEnabled, claimStatus, status, accountStatus, membershipStatus, roleIds, searchTerm, emailDomains }: {
152
284
  /**
153
- * Your organization is identified by a Unique ID. You get your organization ID
154
- * and Organization API key simultaneously.
285
+ * Your organization has a unique ID. Find this ID in your Atlassian
286
+ * Administration URL or when you create your API key.
155
287
  */
156
288
  orgId: string;
157
289
  /**
@@ -175,6 +307,13 @@ export declare class UsersService extends CommonHttpService {
175
307
  resourceIds?: string[] | undefined;
176
308
  /** A list of group IDs. */
177
309
  groupIds?: string[] | undefined;
310
+ /**
311
+ * Whether or not a managed account has two-step verification enabled on their
312
+ * account. If `true`, they have two-step verification enabled.
313
+ * By default, all accounts are returned, regardless of two-step verification
314
+ * status.
315
+ */
316
+ mfaEnabled?: boolean | undefined;
178
317
  /**
179
318
  * The claim status for the user account. By default, both `managed` and
180
319
  * `unmanaged` accounts are returned.
@@ -192,8 +331,10 @@ export declare class UsersService extends CommonHttpService {
192
331
  * - `not_invited` - `accountStatus` is `active` and `membershipStatus` is
193
332
  * `no_membership`.
194
333
  * - `deactivated` - `accountStatus` is `inactive`.
334
+ * - `for_deletion` - Indicates whether or not a managed account is scheduled
335
+ * for deletion.
195
336
  */
196
- status?: ("active" | "suspended" | "not_invited" | "deactivated")[] | undefined;
337
+ status?: ("active" | "suspended" | "not_invited" | "deactivated" | "for_deletion")[] | undefined;
197
338
  /**
198
339
  * The lifecycle status of the account.
199
340
  * - `active` - The account is active and can be used.
@@ -238,9 +379,15 @@ export declare class UsersService extends CommonHttpService {
238
379
  * - `atlassian/ai-access` - Can use AI features in AI-enabled apps they have
239
380
  * access to.
240
381
  */
241
- roleIds?: ("atlassian/user" | "atlassian/user-access-admin" | "atlassian/admin" | "atlassian/guest" | "atlassian/contributor" | "atlassian/customer" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/site-admin" | "atlassian/org-admin" | "atlassian/ai-access")[] | undefined;
382
+ roleIds?: ("atlassian/user" | "atlassian/admin" | "atlassian/guest" | "atlassian/customer" | "atlassian/contributor" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/org-admin" | "atlassian/site-admin" | "atlassian/user-access-admin" | "atlassian/ai-access")[] | undefined;
242
383
  /** A search term to search the `nickname` and `email` fields. */
243
384
  searchTerm?: string | undefined;
385
+ /**
386
+ * The email domain to filter the results. The email domain will be used to search
387
+ * against the account email domain. For example, get all users with the
388
+ * `@atlassian.com` or `@example.com` email domain.
389
+ */
390
+ emailDomains?: string[] | undefined;
244
391
  }) => Promise<{
245
392
  /** The total number of users matching the criteria. */
246
393
  count?: number | undefined;
@@ -258,8 +405,8 @@ export declare class UsersService extends CommonHttpService {
258
405
  */
259
406
  getUserRoleAssignments: ({ orgId, directoryId, accountId, cursor, limit, directoryIds, resourceOwners, resourceIds, roleIds }: {
260
407
  /**
261
- * Your organization is identified by a Unique ID. You get your organization ID
262
- * and Organization API key simultaneously.
408
+ * Your organization has a unique ID. Find this ID in your Atlassian
409
+ * Administration URL or when you create your API key.
263
410
  */
264
411
  orgId: string;
265
412
  /**
@@ -331,7 +478,7 @@ export declare class UsersService extends CommonHttpService {
331
478
  * - `atlassian/ai-access` - Can use AI features in AI-enabled apps they have
332
479
  * access to.
333
480
  */
334
- roleIds?: ("atlassian/user" | "atlassian/user-access-admin" | "atlassian/admin" | "atlassian/guest" | "atlassian/contributor" | "atlassian/customer" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/site-admin" | "atlassian/org-admin" | "atlassian/ai-access")[] | undefined;
481
+ roleIds?: ("atlassian/user" | "atlassian/admin" | "atlassian/guest" | "atlassian/customer" | "atlassian/contributor" | "atlassian/basic" | "atlassian/stakeholder" | "atlassian/org-admin" | "atlassian/site-admin" | "atlassian/user-access-admin" | "atlassian/ai-access")[] | undefined;
335
482
  }) => Promise<MultiDirectoryUserRoleAssignmentPage>;
336
483
  /**
337
484
  * Returns a list of managed accounts in an organization.
@@ -343,25 +490,25 @@ export declare class UsersService extends CommonHttpService {
343
490
  */
344
491
  getUsers: ({ orgId, cursor }: {
345
492
  /**
346
- * Your organization is identified by a Unique ID. You get your organization ID
347
- * and Organization API key simultaneously.
493
+ * Your organization has a unique ID. Find this ID in your Atlassian
494
+ * Administration URL or when you create your API key.
348
495
  */
349
496
  orgId: string;
350
497
  /** Sets the starting point for the page of results to return. */
351
498
  cursor?: string | undefined;
352
499
  }) => Promise<UserPage>;
353
500
  /**
354
- * Returns user stats for the organization.
501
+ * Return user stats for the organization.
355
502
  *
356
- * @returns Returned if the request is successful.
503
+ * @returns Success
357
504
  * @path GET `/v2/orgs/{orgId}/directories/{directoryId}/users/stats`
358
505
  * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-stats-get
359
506
  * @param params
360
507
  */
361
508
  getUserStats: ({ orgId, directoryId }: {
362
509
  /**
363
- * Your organization is identified by a Unique ID. You get your organization ID
364
- * and Organization API key simultaneously.
510
+ * Your organization has a unique ID. Find this ID in your Atlassian
511
+ * Administration URL or when you create your API key.
365
512
  */
366
513
  orgId: string;
367
514
  /**
@@ -372,6 +519,374 @@ export declare class UsersService extends CommonHttpService {
372
519
  directoryId: string;
373
520
  }) => Promise<MultiDirectoryUserStats>;
374
521
  /**
522
+ * **Additional response parameters of the API (for e.g., `added_to_org`) are
523
+ * available only to customers using the new user management experience.** Learn
524
+ * more about the [new user management
525
+ * experience](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592).
526
+ *
527
+ * Specifications:
528
+ * - Return a user’s last active date for each product listed in Atlassian
529
+ * Administration.
530
+ * - Active is defined as viewing a product's page for a minimum of 2 seconds.
531
+ * - The data for the last activity may be delayed by up to 24 hours.
532
+ * - If the user has not accessed a product, the `product_access` response field
533
+ * will be empty.
534
+ *
535
+ * Learn the fastest way to call the API with a detailed
536
+ * [tutorial](https://developer.atlassian.com/cloud/admin/organization/user-last-active-dates/).
537
+ *
538
+ * @returns Successful operation
539
+ * @path GET `/v1/orgs/{orgId}/directory/users/{accountId}/last-active-dates`
540
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-directory-users-accountid-last-active-dates-get
541
+ * @param params
542
+ */
543
+ getV1OrgsOrgIdDirectoryUsersAccountIdLastActiveDates: ({ orgId, accountId, cursor }: {
544
+ /**
545
+ * Your organization has a unique ID. Find this ID in your Atlassian
546
+ * Administration URL or when you create your API key.
547
+ */
548
+ orgId: string;
549
+ /**
550
+ * Unique ID of the user's account.
551
+ * Use the [Jira User Search
552
+ * API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get)
553
+ * to get the accountId (if Jira is available for your Organization). **Jira APIs
554
+ * use a different [authentication method
555
+ * ](https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/).**
556
+ * If you don’t have Jira, export a .csv of the user list. Learn how to [export
557
+ * users from a
558
+ * site](https://support.atlassian.com/organization-administration/docs/export-users-from-a-site/).
559
+ */
560
+ accountId: string;
561
+ /** Cursor to fetch the next page */
562
+ cursor?: string | undefined;
563
+ }) => Promise<UserProductAccessActivityPage>;
564
+ /**
565
+ * **This API is deprecated and will no longer work after June 30, 2026.** Use the
566
+ * [Restore user access in directory
567
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-accountid-restore-post)
568
+ * instead.
569
+ *
570
+ * **The API is available for customers using the new user management experience
571
+ * only.** Learn more about the [new user management
572
+ * experience](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592).
573
+ *
574
+ * This API will:
575
+ * - Restore access of an existing user to products listed in Atlassian
576
+ * Administration.
577
+ * - Retract the suspend user action.
578
+ *
579
+ * This API will not:
580
+ * - Restore access to a user when they have access to a product which is
581
+ * breaching it's license limit.\
582
+ * To make these changes, you will need to [remove
583
+ * users](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v1-orgs-orgid-directory-groups-groupid-memberships-accountid-delete)
584
+ * from the group or
585
+ * [suspend
586
+ * users](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v1-orgs-orgid-directory-users-accountid-suspend-access-post)
587
+ * that are in the group first.\
588
+ * You can also [manage your
589
+ * subscription](https://support.atlassian.com/subscriptions-and-billing/resources/)
590
+ * for the breaching product to increase your license limits.
591
+ * - Restore access to any user when your organisation has too many products that
592
+ * are breaching their license limits.
593
+ *
594
+ * Learn the fastest way to call the API with a detailed
595
+ * [tutorial](https://developer.atlassian.com/cloud/admin/organization/restore-user/).
596
+ *
597
+ * @deprecated
598
+ * @returns User's access is successfully restored in the organization directory.
599
+ * @path POST `/v1/orgs/{orgId}/directory/users/{accountId}/restore-access`
600
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-directory-users-accountid-restore-access-post
601
+ * @param params
602
+ */
603
+ postV1OrgsOrgIdDirectoryUsersAccountIdRestoreAccess: ({ orgId, accountId }: {
604
+ /**
605
+ * Your organization has a unique ID. Find this ID in your Atlassian
606
+ * Administration URL or when you create your API key.
607
+ */
608
+ orgId: string;
609
+ /**
610
+ * Unique ID of the user's account that you are suspending.
611
+ * Use the [Jira User Search
612
+ * API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get)
613
+ * to get the accountId (if Jira is available for your Organization). **Jira APIs
614
+ * use a different [authentication method
615
+ * ](https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/).**
616
+ * If you don’t have Jira, export a .csv of the user list. Learn how to [export
617
+ * users from a
618
+ * site](https://support.atlassian.com/organization-administration/docs/export-users-from-a-site/).
619
+ */
620
+ accountId: string;
621
+ }) => Promise<{
622
+ /**
623
+ * A description of the entities affected, and changes made as a result of calling
624
+ * this API.
625
+ *
626
+ * @example
627
+ * Access to organization 6665kc2j-4644-14k8-j32c-68cc0b1d15b8 was restored for user 637194fa77acd224b33bfae3
628
+ */
629
+ message?: string | undefined;
630
+ } & {
631
+ [key: string]: unknown;
632
+ }>;
633
+ /**
634
+ * **This API is deprecated and will no longer work after June 30, 2026.** Use the
635
+ * [Suspend user access in directory
636
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-accountid-suspend-post)
637
+ * instead.
638
+ *
639
+ * **The API is available for customers using the new user management experience
640
+ * only.** Learn more about the [new user management
641
+ * experience](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592).
642
+ *
643
+ * Specifications:
644
+ * - Suspend user access to products listed in Atlassian Administration while
645
+ * keeping the account active.
646
+ * - Make product licenses available for active users.
647
+ * - Maintain respective users in **Groups** for easy restoration.
648
+ *
649
+ * User access can be restored anytime via the [Restore access
650
+ * API](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v1-orgs-orgid-directory-users-accountid-restore-access-post)
651
+ *
652
+ * Learn the fastest way to call the API with a detailed
653
+ * [tutorial](https://developer.atlassian.com/cloud/admin/organization/suspend-user/).
654
+ *
655
+ * @deprecated
656
+ * @returns User was successfully suspended in the organization directory.
657
+ * @path POST `/v1/orgs/{orgId}/directory/users/{accountId}/suspend-access`
658
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-directory-users-accountid-suspend-access-post
659
+ * @param params
660
+ */
661
+ postV1OrgsOrgIdDirectoryUsersAccountIdSuspendAccess: ({ orgId, accountId }: {
662
+ /**
663
+ * Your organization has a unique ID. Find this ID in your Atlassian
664
+ * Administration URL or when you create your API key.
665
+ */
666
+ orgId: string;
667
+ /**
668
+ * Unique ID of the user's account that you are suspending.
669
+ * Use the [Jira User Search
670
+ * API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-users-search-get)
671
+ * to get the accountId (if Jira is available for your Organization). **Jira APIs
672
+ * use a different [authentication method
673
+ * ](https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/).**
674
+ * If you don’t have Jira, export a .csv of the user list. Learn how to [export
675
+ * users from a
676
+ * site](https://support.atlassian.com/organization-administration/docs/export-users-from-a-site/).
677
+ */
678
+ accountId: string;
679
+ }) => Promise<{
680
+ /**
681
+ * A description of the entities affected, and changes made as a result of calling
682
+ * this API.
683
+ *
684
+ * @example
685
+ * Access to organization 6665kc2j-4644-14k8-j32c-68cc0b1d15b8 was suspended for user 637194fa77acd224b33bfae3
686
+ */
687
+ message?: string | undefined;
688
+ } & {
689
+ [key: string]: unknown;
690
+ }>;
691
+ /**
692
+ * **The API is presently accessible exclusively to customers who hold a paid
693
+ * subscription.**
694
+ *
695
+ * **The API is available for customers using the [new user management experience
696
+ * only](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592)**.
697
+ *
698
+ * This API will:
699
+ * - invite user to org and add them to the directory
700
+ * - assign a role for a given resource
701
+ * - send email if the sendNotification field is set true with optional custom
702
+ * message for the email
703
+ *
704
+ * This API will not:
705
+ * - add users to group
706
+ *
707
+ * @deprecated
708
+ * @returns Invitation successfully sent
709
+ * @path POST `/v1/orgs/{orgId}/users/invite`
710
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-users-invite-post
711
+ * @param params
712
+ */
713
+ postV1OrgsOrgIdUsersInvite: ({ orgId, inviteApiRequest }: {
714
+ /**
715
+ * Your organization has a unique ID. Find this ID in your Atlassian
716
+ * Administration URL or when you create your API key.
717
+ */
718
+ orgId: string;
719
+ inviteApiRequest: InviteApiRequest;
720
+ }) => Promise<string[]>;
721
+ /**
722
+ * Assign an organization-level role to a user. These are roles that have
723
+ * organization-wide privileges, like organization admin.
724
+ *
725
+ * This operation follows eventual consistency. Changes may take up to 30 seconds
726
+ * to be reflected after the operation is performed.
727
+ *
728
+ * @path POST `/v1/orgs/{orgId}/users/{userId}/role-assignments/assign`
729
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-users-userid-role-assignments-assign-post
730
+ * @param params
731
+ */
732
+ postV1OrgsOrgIdUsersUserIdRoleAssignmentsAssign: ({ orgId, userId, organizationLevelRoleApiRequest }: {
733
+ /**
734
+ * Your organization has a unique ID. Find this ID in your Atlassian
735
+ * Administration URL or when you create your API key.
736
+ */
737
+ orgId: string;
738
+ /**
739
+ * Every user has a unique ID. Find a user’s account ID by using the [Get users
740
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get).
741
+ */
742
+ userId: string;
743
+ organizationLevelRoleApiRequest: OrganizationLevelRoleApiRequest;
744
+ }) => Promise<void>;
745
+ /**
746
+ * Remove an organization-level role from a user. These are roles that have
747
+ * organization-wide privileges, like organization admin.
748
+ *
749
+ * This operation follows eventual consistency. Changes may take up to 30 seconds
750
+ * to be reflected after the operation is performed.
751
+ *
752
+ * @path POST `/v1/orgs/{orgId}/users/{userId}/role-assignments/revoke`
753
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-users-userid-role-assignments-revoke-post
754
+ * @param params
755
+ */
756
+ postV1OrgsOrgIdUsersUserIdRoleAssignmentsRevoke: ({ orgId, userId, organizationLevelRoleApiRequest }: {
757
+ /**
758
+ * Your organization has a unique ID. Find this ID in your Atlassian
759
+ * Administration URL or when you create your API key.
760
+ */
761
+ orgId: string;
762
+ /**
763
+ * Every user has a unique ID. Find a user's account ID by using the [Get users
764
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get).
765
+ */
766
+ userId: string;
767
+ organizationLevelRoleApiRequest: OrganizationLevelRoleApiRequest;
768
+ }) => Promise<void>;
769
+ /**
770
+ * Restore a user’s access in a directory to let them access apps again. They
771
+ * regain their roles and group memberships from before their access was
772
+ * suspended. We resume billing you for this user.
773
+ *
774
+ * @path POST `/v2/orgs/{orgId}/directories/{directoryId}/users/{accountId}/restore`
775
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-accountid-restore-post
776
+ * @param params
777
+ */
778
+ postV2OrgsOrgIdDirectoriesDirectoryIdUsersAccountIdRestore: ({ orgId, directoryId, accountId }: {
779
+ /**
780
+ * Your organization has a unique ID. Find this ID in your Atlassian
781
+ * Administration URL or when you create your API key.
782
+ */
783
+ orgId: string;
784
+ /**
785
+ * A directory has a unique ID. Use the [Get directories
786
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v2-orgs-orgid-directories-get)
787
+ * to find the directory ID.
788
+ */
789
+ directoryId: string;
790
+ /**
791
+ * Every user has a unique ID. Find a user’s account ID by using the [Get users
792
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get).
793
+ */
794
+ accountId: string;
795
+ }) => Promise<void>;
796
+ /**
797
+ * Suspend a user’s access in a directory to remove their access to apps
798
+ * temporarily. You’re not billed for a user when their access is suspended. They
799
+ * regain their roles and group memberships when you restore their access.
800
+ *
801
+ * @path POST `/v2/orgs/{orgId}/directories/{directoryId}/users/{accountId}/suspend`
802
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-directories-directoryid-users-accountid-suspend-post
803
+ * @param params
804
+ */
805
+ postV2OrgsOrgIdDirectoriesDirectoryIdUsersAccountIdSuspend: ({ orgId, directoryId, accountId }: {
806
+ /**
807
+ * Your organization has a unique ID. Find this ID in your Atlassian
808
+ * Administration URL or when you create your API key.
809
+ */
810
+ orgId: string;
811
+ /**
812
+ * A directory has a unique ID. Use the [Get directories
813
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-directory/#api-v2-orgs-orgid-directories-get)
814
+ * to find the directory ID.
815
+ */
816
+ directoryId: string;
817
+ /**
818
+ * Every user has a unique ID. Find a user’s account ID by using the [Get users
819
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get).
820
+ */
821
+ accountId: string;
822
+ }) => Promise<void>;
823
+ /**
824
+ * Invite people to your organization. When you invite someone:
825
+ * - they’re given app roles according to your invitation.
826
+ * - they’re added to directories based on apps in your invitation.
827
+ * - they’re added to groups according to your invitation.
828
+ * - they receive an email invitation if the `sendNotification` field is set to
829
+ * `true` and the `notificationText` field contains a message to include in the
830
+ * email invitation.
831
+ *
832
+ * **This API is only available to customers who have at least one paid
833
+ * subscription in their organization.**
834
+ *
835
+ * @returns
836
+ * * status: 200, mediaType: application/json
837
+ *
838
+ * Success
839
+ *
840
+ * * status: 206, mediaType: application/json
841
+ *
842
+ * At least one invitation failed
843
+ * @path POST `/v2/orgs/{orgId}/users/invite`
844
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v2-orgs-orgid-users-invite-post
845
+ * @param params
846
+ */
847
+ postV2OrgsOrgIdUsersInvite: ({ orgId, multidirectoryInviteApiRequest }: {
848
+ /**
849
+ * Your organization has a unique ID. Find this ID in your Atlassian
850
+ * Administration URL or when you create your API key.
851
+ */
852
+ orgId: string;
853
+ multidirectoryInviteApiRequest: MultidirectoryInviteApiRequest;
854
+ }) => Promise<commonHttpClient.WithResponse<{
855
+ status: 200 | 206;
856
+ mediaType: "application/json";
857
+ body: MultidirectoryInviteSuccessResponse;
858
+ }>>;
859
+ /**
860
+ * **The API is available for customers using the [new user management experience
861
+ * only](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592)**.
862
+ *
863
+ * This API can be used to revoke Platform Roles from a user.
864
+ *
865
+ * @path POST `/v1/orgs/{orgId}/users/{userId}/roles/revoke`
866
+ * @see https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users#api-v1-orgs-orgid-users-userid-roles-revoke-post
867
+ * @param params
868
+ */
869
+ revokeRole: ({ orgId, userId, roleApiRequest }: {
870
+ /**
871
+ * Your organization has a unique ID. Find this ID in your Atlassian
872
+ * Administration URL or when you create your API key.
873
+ */
874
+ orgId: string;
875
+ /**
876
+ * The UserId on which the action(Role Revoke) needs to happen. Use the [Search
877
+ * for users within an organization
878
+ * API](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v1-orgs-orgid-users-get)
879
+ * to get the userId.
880
+ */
881
+ userId: string;
882
+ roleApiRequest: RoleApiRequest;
883
+ }) => Promise<void>;
884
+ /**
885
+ * **This API is deprecated and will no longer work after June 30, 2026.** Use the
886
+ * [Get users in an organization
887
+ * endpoint](https://developer.atlassian.com/cloud/admin/organization/rest/api-group-users/#api-v2-orgs-orgid-directories-directoryid-users-get)
888
+ * instead.
889
+ *
375
890
  * **The API is available for customers using the new user management experience
376
891
  * only. [How the new user management experience
377
892
  * works](https://community.atlassian.com/t5/Atlassian-Access-articles/User-management-for-cloud-admins-just-got-easier/ba-p/1576592)**
@@ -379,6 +894,7 @@ export declare class UsersService extends CommonHttpService {
379
894
  * Returns a list of users within an organization, offering search functionality
380
895
  * through multiple parameters for more precise results.
381
896
  *
897
+ * @deprecated
382
898
  * @returns Organization found. Response contains user search results
383
899
  *
384
900
  * example: " users_search_response":
@@ -403,8 +919,8 @@ export declare class UsersService extends CommonHttpService {
403
919
  */
404
920
  searchUsers: ({ orgId, usersSearchRequest }: {
405
921
  /**
406
- * Your organization is identified by a Unique ID. You get your organization ID
407
- * and Organization API key simultaneously.
922
+ * Your organization has a unique ID. Find this ID in your Atlassian
923
+ * Administration URL or when you create your API key.
408
924
  */
409
925
  orgId: string;
410
926
  /**