removed md from gitignore

.gitignore

@@ -19,10 +19,10 @@ npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
 
-/products/arm/api
-/products/idn/api/v3
-products/idn/api/beta
-/products/iiq/api
+# /products/arm/api
+# /products/idn/api/v3
+# /products/idn/api/beta
+# /products/iiq/api
 
 #Alogolia env file
 /algolia/.env

products/idn/api/beta/access-profiles.tag.mdx

@@ -0,0 +1,54 @@
+---
+id: access-profiles
+title: "Access Profiles"
+description: "Access Profiles"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement and customize access profile functionality.
+With this functionality in place, administrators can create access profiles and configure them for use throughout IdentityNow, enabling users to get the access they need quickly and securely.
+
+Access profiles group entitlements, which represent access rights on sources.
+
+For example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.
+
+An administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.
+
+When users only need Active Directory employee access, they can request access to the 'Employees' entitlement.
+
+When users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.
+
+Access profiles are the most important units of access in IdentityNow. IdentityNow uses access profiles in many features, including the following:
+
+- Provisioning: When you use the Provisioning Service, lifecycle states and roles both grant access to users in the form of access profiles.
+
+- Certifications: You can approve or revoke access profiles in certification campaigns, just like entitlements.
+
+- Access Requests: You can assign access profiles to applications, and when a user requests access to the app associated with an access profile and someone approves the request, access is granted to both the application and its associated access profile.
+
+- Roles: You can group one or more access profiles into a role to quickly assign access items based on an identity's role.
+
+In IdentityNow, administrators can use the Access drop-down menu and select Access Profiles to view, configure, and delete existing access profiles, as well as create new ones.
+Administrators can enable and disable an access profile, and they can also make the following configurations:
+
+- Manage Entitlements: Manage the profile's access by adding and removing entitlements.
+
+- Access Requests: Configure access profiles to be requestable and establish an approval process for any requests that the access profile be granted or revoked.
+Do not configure an access profile to be requestable without first establishing a secure access request approval process for the access profile.
+
+- Multiple Account Options: Define the logic IdentityNow uses to provision access to an identity with multiple accounts on the source.
+
+Refer to [Managing Access Profiles](https://documentation.sailpoint.com/saas/help/access/access-profiles.html) for more information about access profiles.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/access-request-approvals.tag.mdx

@@ -0,0 +1,37 @@
+---
+id: access-request-approvals
+title: "Access Request Approvals"
+description: "Access Request Approvals"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement and customize access request approval functionality.
+With this functionality in place, administrators can delegate qualified users to review users' requests for access or managers' requests to revoke team members' access to applications, entitlements, or roles.
+This enables more qualified users to review access requests and the others to spend their time on other tasks.
+
+In IdentityNow, users can request access to applications, entitlements, and roles, and managers can request that team members' access be revoked.
+For applications and entitlements, administrators can set access profiles to require approval from the access profile owner, the application owner, the source owner, the requesting user's manager, or a governance group for access to be granted or revoked.
+For roles, administrators can also set roles to allow access requests and require approval from the role owner, the requesting user's manager, or a governance group for access to be granted or revoked.
+If the administrator designates a governance group as the required approver, any governance group member can approve the requests.
+
+When a user submits an access request, IdentityNow sends the first required approver in the queue an email notification, based on the access request configuration's approval and reminder escalation configuration.
+
+In Approvals in IdentityNow, required approvers can view pending access requests under the Requested tab and approve or deny them, or the approvers can reassign the requests to different reviewers for approval.
+If the required approver approves the request and is the only reviewer required, IdentityNow grants or revokes access, based on the request.
+If multiple reviewers are required, IdentityNow sends the request to the next reviewer in the queue, based on the access request configuration's approval reminder and escalation configuration.
+The required approver can then view any completed access requests under the Reviewed tab.
+
+Refer to [Access Requests](https://documentation.sailpoint.com/saas/help/requests/index.html) for more information about access request approvals.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/access-requests.tag.mdx

@@ -0,0 +1,35 @@
+---
+id: access-requests
+title: "Access Requests"
+description: "Access Requests"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement and customize access request functionality.
+With this functionality in place, users can request access to applications, entitlements, or roles, and managers can request that team members' access be revoked.
+This allows users to get access to the tools they need quickly and securely, and it allows managers to take away access to those tools.
+
+IdentityNow's Access Request service allows end users to request access that requires approval before it can be granted to users and enables qualified users to review those requests and approve or deny them.
+
+In the Request Center in IdentityNow, users can view available applications, roles, and entitlements and request access to them.
+If the requested tools requires approval, the requests appear as 'Pending' under the My Requests tab until the required approver approves, rejects, or cancels them.
+
+Users can use My Requests to track and/or cancel the requests.
+
+In My Team on the IdentityNow Home, managers can submit requests to revoke their team members' access.
+They can use the My Requests tab under Request Center to track and/or cancel the requests.
+
+Refer to [Requesting Access](https://documentation.sailpoint.com/saas/user-help/requests/requesting_access.html) for more information about access requests.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/account-activities.tag.mdx

@@ -0,0 +1,53 @@
+---
+id: account-activities
+title: "Account Activities"
+description: "Account Activities"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement account activity tracking functionality.
+With this functionality in place, users can track source account activity in IdentityNow, which greatly improves traceability in the system.
+
+An account activity refers to a log of each action performed on a source account. This is useful for auditing the changes that occur on an account throughout its life.
+In IdentityNow's Search, users can search for account activities and select the activity's row to get an overview of the activity's account action and view its progress, its involved sources, and its most basic metadata, such as the identity requesting the option and the recipient.
+
+Account activity includes most actions IdentityNow completes on source accounts. Users can search in IdentityNow for the following account action types:
+
+- Access Request: These include any access requests the source account is involved in.
+
+- Account Attribute Updates: These include updates to a single attribute on an account on a source.
+
+- Account State Update: These include locking or unlocking actions on an account on a source.
+
+- Certification: These include actions removing an entitlement from an account on a source as a result of the entitlement's revocation during a certification.
+
+- Cloud Automated `Lifecyclestate`: These include automated lifecycle state changes that result in a source account's correlated identity being assigned to a different lifecycle state.
+IdentityNow replaces the `Lifecyclestate` variable with the name of the lifecycle state it has moved the account's identity to.
+
+- Identity Attribute Update: These include updates to a source account's correlated identity attributes as the result of a provisioning action.
+When you update an identity attribute that also updates an identity's lifecycle state, the cloud automated `Lifecyclestate` event also displays.
+Account Activity does not include attribute updates that occur as a result of aggregation.
+
+- Identity Refresh: These include correlated identity refreshes that occur for an account on a source whenever the account's correlated identity profile gets a new role or updates.
+These also include refreshes that occur whenever IdentityNow assigns an application to the account's correlated identity based on the application's being assigned to All Users From Source or Specific Users From Source.
+
+- Lifecycle State Refresh: These include the actions that took place when a lifecycle state changed. This event only occurs after a cloud automated `Lifecyclestate` change or a lifecycle state change.
+
+- Lifecycle State Change: These include the account activities that result from an identity's manual assignment to a null lifecycle state.
+
+- Password Change: These include password changes on sources.
+
+Refer to [Account Activity](https://documentation.sailpoint.com/saas/help/search/index.html#account-activity) for more information about account activities.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/account-aggregations.tag.mdx

@@ -0,0 +1,30 @@
+---
+id: account-aggregations
+title: "Account Aggregations"
+description: "Account Aggregations"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement account aggregation progress tracking functionality.
+With this functionality in place, administrators can view in-progress account aggregations, their statuses, and their relevant details.
+
+An account aggregation refers to the process IdentityNow uses to gather and load account data from a source into IdentityNow.
+
+Whenever IdentityNow is in the process of aggregating a source, it adds an entry to the Aggregation Activity Log, along with its relevant details.
+To view aggregation activity, administrators can select the Connections drop-down menu, select Sources, and select the relevant source, select its Import Data tab, and select Account Aggregation.
+In Account Aggregation, administrators can view the account aggregations' statuses and details in the Account Activity Log.
+
+Refer to [Loading Account Data](https://documentation.sailpoint.com/saas/help/accounts/loading_data.html) for more information about account aggregations.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/accounts.tag.mdx

@@ -0,0 +1,47 @@
+---
+id: accounts
+title: "Accounts"
+description: "Accounts"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement and customize account functionality.
+With this functionality in place, administrators can manage users' access across sources in IdentityNow.
+
+In IdentityNow, an account refers to a user's account on a supported source.
+This typically includes a unique identifier for the user, a unique password, a set of permissions associated with the source and a set of attributes. IdentityNow loads accounts through the creation of sources in IdentityNow.
+
+Administrators can correlate users' identities with the users' accounts on the different sources they use.
+This allows IdentityNow to govern the access of identities and all their correlated accounts securely and cohesively.
+
+To view the accounts on a source and their correlated identities, administrators can use the Connections drop-down menu, select Sources, select the relevant source, and select its Account tab.
+
+To view and edit source account statuses for an identity in IdentityNow, administrators can use the Identities drop-down menu, select Identity List, select the relevant identity, and select its Accounts tab.
+Administrators can toggle an account's Actions to aggregate the account, enable/disable it, unlock it, or remove it from the identity.
+
+Accounts can have the following statuses:
+
+- Enabled: The account is enabled. The user can access it.
+
+- Disabled: The account is disabled, and the user cannot access it, but the identity is not disabled in IdentityNow. This can occur when an administrator disables the account or when the user's lifecycle state changes.
+
+- Locked: The account is locked. This may occur when someone has entered an incorrect password for the account too many times.
+
+- Pending: The account is currently updating. This status typically lasts seconds.
+
+Administrators can select the source account to view its attributes, entitlements, and the last time the account's password was changed.
+
+Refer to [Managing User Accounts](https://documentation.sailpoint.com/saas/help/common/users/user_access.html#managing-user-accounts) for more information about accounts.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/certification-campaigns.tag.mdx

@@ -0,0 +1,85 @@
+---
+id: certification-campaigns
+title: "Certification Campaigns"
+description: "Certification Campaigns"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement certification campaign functionality.
+With this functionality in place, administrators can create, customize, and manage certification campaigns for their organizations' use.
+Certification campaigns provide IdentityNow (IDN) users with an interactive review process they can use to identify and verify access to systems.
+Campaigns help organizations reduce risk of inappropriate access and satisfy audit requirements.
+
+A certification refers to IDN's mechanism for reviewing a user's access to entitlements (sets of permissions) and approving or removing that access.
+These certifications serve as a way of showing that a user's access has been reviewed and approved.
+Multiple certifications by different reviewers are often required to approve a user's access.
+A set of multiple certifications is called a certification campaign.
+
+For example, an organization may use a Manager Certification campaign as a way of showing that a user's access has been reviewed and approved by multiple managers.
+Once this campaign has been completed, IDN would provision all the access the user needs, nothing more.
+
+IDN provides two simple campaign types users can create without using search queries, Manager and Source Owner campaigns:
+
+You can create these types of campaigns without using any search queries in IDN:
+
+- ManagerCampaign: IDN provides this campaign type as a way to ensure that an identity's access is certified by their managers.
+You only need to provide a name and description to create one.
+
+- Source Owner Campaign: IDN provides this campaign type as a way to ensure that an identity's access to a source is certified by its source owners.
+You only need to provide a name and description to create one.
+You can specify the sources whose owners you want involved or just run it across all sources.
+
+For more information about these campaign types, refer to [Starting a Manager or Source Owner Campaign](https://documentation.sailpoint.com/saas/help/certs/starting_campaign.html).
+
+One useful way to create certification campaigns in IDN is to use a specific search and then run a campaign on the results returned by that search.
+This allows you to be much more specific about whom you are certifying in your campaigns and what access you are certifying in your campaigns.
+For example, you can search for all identities who are managed by "Amanda.Ross" and also have the access to the "Accounting" role and then run a certification campaign based on that search to ensure that the returned identities are appropriately certified.
+
+You can use IDN search queries to create these types of campaigns:
+
+- Identities: Use this campaign type to review and revoke access items for specific identities.
+You can either build a search query and create a campaign certifying all identities returned by that query, or you can search for individual identities and add those identities to the certification campaign.
+
+- Access Items: Use this campaign type to review and revoke a set of roles, access profiles, or entitlements from the identities that have them.
+You can either build a search query and create a campaign certifying all access items returned by that query, or you can search for individual access items and add those items to the certification campaign.
+
+- Role Composition: Use this campaign type to review a role's composition, including its title, description, and membership criteria.
+You can either build a search query and create a campaign certifying all roles returned by that query, or you can search for individual roles and add those roles to the certification campaign.
+
+- Uncorrelated Accounts: Use this campaign type to certify source accounts that aren't linked to an authoritative identity in IDN.
+You can use this campaign type to view all the uncorrelated accounts for a source and certify them.
+
+For more information about search-based campaigns, refer to [Starting a Campaign from Search](https://documentation.sailpoint.com/saas/help/certs/starting_search_campaign.html).
+
+Once you have generated your campaign, it becomes available for preview.
+An administrator can review the campaign and make changes, or if it's ready and accurate, activate it.
+
+Once the campaign is active, organization administrators or certification administrators can designate other IDN users as certification reviewers.
+Those reviewers can view any of the certifications they either need to review (active) or have already reviewed (completed).
+
+When a certification campaign is in progress, certification reviewers see the listed active certifications whose involved identities they can review.
+Reviewers can then make decisions to grant or revoke access, as well as reassign the ceritifcation to another reviewer. If the reviewer chooses this option, they must provide a reason for reassignment in the form of a comment.
+
+Once a reviewer has made decisions on all the certification's involved access items, he or she must "Sign Off" to complete the review process.
+Doing so converts the certification into read-only status, preventing any further changes to the review decisions and deleting the work item (task) from the reviewer's list of work items.
+
+Once all the reviewers have signed off, the certification campaign either completes or, if any reviewers decided to revoke access for any of the involved identities, it moves into a remediation phase.
+In the remediation phase, identities' entitlements are altered to remove any entitlements marked for revocation.
+In this situation, the certification campaign completes once all the remediation requests are completed.
+
+The end of a certification campaign is determined by its deadline, its completion status, or by an administrator's decision.
+
+For more information about certifications and certification campaigns, refer to [Certifications](https://documentation.sailpoint.com/saas/user-help/certifications.html).
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/certifications.tag.mdx

@@ -0,0 +1,33 @@
+---
+id: certifications
+title: "Certifications"
+description: "Certifications"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement certification functionality.
+This API provides specific functionality that improves an organization's ability to manage its certification process.
+
+A certification refers to IdentityNow's mechanism for reviewing a user's access to entitlements (sets of permissions) and approving or removing that access.
+These certifications serve as a way of showing that a user's access has been reviewed and approved.
+Multiple certifications by different reviewers are often required to approve a user's access.
+A set of multiple certifications is called a certification campaign.
+
+For example, an organization may use a Manager Certification as a way of showing that a user's access has been reviewed and approved by their manager, or if the certification is part of a campaign, that the user's access has been reviewed and approved by multiple managers.
+Once this certification has been completed, IdentityNow  would provision all the access the user needs, nothing more.
+
+This API enables administrators and reviewers to get useful information about certifications at a high level, such as the reviewers involved, and at a more granular level, such as the permissions affected by changes to entitlements within those certifications.
+It also provides the useful ability to reassign identities and items within certifications to other reviewers, rather than [reassigning the entire certifications themselves](https://developer.sailpoint.com/idn/api/beta/reassign-identity-certs-async).
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/connector-rule-management.tag.mdx

@@ -0,0 +1,16 @@
+---
+id: connector-rule-management
+title: "Connector Rule Management"
+description: "Connector Rule Management"
+custom_edit_url: null
+---
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/connectors.tag.mdx

@@ -0,0 +1,34 @@
+---
+id: connectors
+title: "Connectors"
+description: "Connectors"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement connector functionality.
+With this functionality in place, administrators can view available connectors.
+
+Connectors are the bridges IdentityNow uses to communicate with and aggregate data from sources.
+For example, if it is necessary to set up a connection between IdentityNow and the Active Directory source, a connector can bridge the two and enable IdentityNow to synchronize data between the systems.
+This ensures account entitlements and states are correct throughout the organization.
+
+In IdentityNow, administrators can use the Connections drop-down menu and select Sources to view the available source connectors.
+
+Refer to [IdentityNow Connectors](https://documentation.sailpoint.com/connectors/identitynow/landingpages/help/landingpages/identitynow_connectivity_landing.html) for more information about the connectors available in IdentityNow.
+
+Refer to [SaaS Connectivity](https://developer.sailpoint.com/idn/docs/saas-connectivity) for more information about the SaaS custom connectors that do not need VAs (virtual appliances) to communicate with their sources.
+
+Refer to [Managing Sources](https://documentation.sailpoint.com/saas/help/sources/managing_sources.html) for more information about using connectors in IdentityNow.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/custom-forms.tag.mdx

@@ -0,0 +1,28 @@
+---
+id: custom-forms
+title: "Custom Forms"
+description: "Custom Forms"
+custom_edit_url: null
+---
+
+
+
+Use this API to build and manage custom forms.
+With this functionality in place, administrators can create and view form definitions and form instances.
+
+Forms are composed of sections and fields. Sections split the form into logical groups of fields and fields are the data collection points within the form. Configure conditions to modify elements of the form as the responder provides input. Create form inputs to pass information from a calling feature, like a workflow, to your form.
+
+Forms can be used within workflows as an action or as a trigger. The Form Action allows you to assign a form as a step in a running workflow, suspending the workflow until the form is submitted or times out, and the workflow resumes. The Form Submitted Trigger initiates a workflow when a form is submitted. The trigger can be configured to initiate on submission of a full form, a form element with any value, or a form element with a particular value.
+
+Refer to [Forms](https://documentation.sailpoint.com/saas/help/forms/index.html) for more information about using forms in IdentityNow.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+      

products/idn/api/beta/custom-password-instructions.tag.mdx

@@ -0,0 +1,31 @@
+---
+id: custom-password-instructions
+title: "Custom Password Instructions"
+description: "Custom Password Instructions"
+custom_edit_url: null
+---
+
+
+
+Use this API to implement custom password instruction functionality.
+With this functionality in place, administrators can create custom password instructions to help users reset their passwords, change them, unlock their accounts, or recover their usernames.
+This allows administrators to emphasize password policies or provide organization-specific instructions.
+
+Administrators must first use [Update Password Org Config](https://developer.sailpoint.com/idn/api/beta/update-password-org-config) to set `customInstructionsEnabled` to `true`.
+
+Once they have enabled custom instructions, they can use [Create Custom Password Instructions](https://developer.sailpoint.com/idn/api/beta/create-custom-password-instructions) to create custom page content for the specific pageId they select.
+
+For example, an administrator can use the pageId forget-username:user-email to set the custom text for the case when users forget their usernames and must enter their emails.
+
+Refer to [Creating Custom Instruction Text](https://documentation.sailpoint.com/saas/help/pwd/pwd_reset.html#creating-custom-instruction-text) for more information about creating custom password instructions.
+
+
+
+
+```mdx-code-block
+import DocCardList from '@theme/DocCardList';
+import {useCurrentSidebarCategory} from '@docusaurus/theme-common';
+
+<DocCardList items={useCurrentSidebarCategory().items}/>
+```
+