Skip to content

Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.

fixes and address codex

Adrian Kahali81d2b33bfed5
diff --git a/docs/documentation/platform/access-controls/abac/managing-user-metadata.mdx b/docs/documentation/platform/access-controls/abac/managing-user-metadata.mdx
index 0583915cf1..64af36e6bc 100644
--- a/docs/documentation/platform/access-controls/abac/managing-user-metadata.mdx
+++ b/docs/documentation/platform/access-controls/abac/managing-user-metadata.mdx
@@ -10,13 +10,19 @@ User identities can have metadata attributes assigned directly. These attributes
<Tabs>
<Tab title="Manually Configure Metadata">
<Steps>
- <Step title="Navigate to the Access Control page on the organization sidebar and select a user.">
+ <Step title="Open a user">
+ In the organization sidebar, select **Access Control**, select **Users**, then select a user.
+
<img src="/images/platform/access-controls/add-metadata-step1.png" />
</Step>
- <Step title="On the User Page, click the pencil icon to edit the selected user.">
+ <Step title="Open the user editor">
+ Select **Options**, then select **Edit User**.
+
<img src="/images/platform/access-controls/add-metadata-step2.png" />
</Step>
- <Step title="Add metadata via key-value pairs and update the user identity.">
+ <Step title="Add metadata">
+ Select **Add Key**, enter the metadata key-value pair, then select **Update**.
+
<img src="/images/platform/access-controls/add-metadata-step3.png" />
</Step>
</Steps>
diff --git a/docs/documentation/platform/access-controls/project-access-requests.mdx b/docs/documentation/platform/access-controls/project-access-requests.mdx
index 8de9ddd342..fc80bcb278 100644
--- a/docs/documentation/platform/access-controls/project-access-requests.mdx
+++ b/docs/documentation/platform/access-controls/project-access-requests.mdx
@@ -3,7 +3,7 @@ title: "Project access requests"
description: "Learn how to request access to projects in Infisical."
---
-The Project Access Request feature allows users to view all projects within organization, including those they don't currently have access to.
+The Project Access Request feature allows users to view all projects within an organization, including those they don't currently have access to.
Users can request access to these projects by submitting a request that automatically notifies project administrators via email, along with any comments provided by the user.
# Viewing available projects
@@ -22,13 +22,13 @@ From the Infisical dashboard, users can view all projects within the organizatio
To request access to a project you don't currently have access for:
-1. Click the **Request Access** button next to the project name
+1. Select **Request Access** next to the project name
![all-project-view](/images/platform/project-access-requests/request-access.png)
2. Add a comment explaining why you need access
![all-project-view](/images/platform/project-access-requests/access-comment.png)
-3. Click **Submit Request**
+3. Select **Submit Request**
<Info>
Project administrators will receive email notification with details regarding
diff --git a/docs/documentation/platform/access-controls/role-based-access-controls.mdx b/docs/documentation/platform/access-controls/role-based-access-controls.mdx
index 8cc14f4310..a07f4d17c7 100644
--- a/docs/documentation/platform/access-controls/role-based-access-controls.mdx
+++ b/docs/documentation/platform/access-controls/role-based-access-controls.mdx
@@ -12,7 +12,7 @@ In general, access controls can be split up across [organizations](/documentatio
Every user and machine identity in an organization is assigned one of the following built-in roles:
- **Admin**: Full control over the organization, including adding and removing members, managing access controls, configuring security settings, setting up identity providers, managing billing, and creating new projects.
-- **Member**: Can access projects they are added to and perform day-to-day actions, but is restricted from removing organization members, modifying billing information, updating organization-level access controls, and performing other administrative actions. This is the default role assigned to new members.
+- **Member**: Can access projects they're added to and perform day-to-day actions, but is restricted from removing organization members, modifying billing information, updating organization-level access controls, and performing other administrative actions. This is the default role assigned to new members.
- **No Access**: No permissions at the organization level. This role is useful when you want to grant access exclusively through project-level roles or [Additional Privileges](/documentation/platform/access-controls/additional-privileges).
Organization-level access controls are primarily administrative in nature. Access to projects, secrets, and other sensitive data is specified at the project level.
@@ -25,7 +25,7 @@ Every user and machine identity in a project is assigned one of the following bu
- **Admin**: Full access to all environments, folders, secrets, and actions within the project. Admins can manage project members, configure roles, set up Approval Workflow policies, and perform all other project-level operations.
- **Member**: Read and write access to secrets, folders, secret imports, integrations, webhooks, and other day-to-day resources across all environments. Members are restricted from performing administrative actions such as managing roles, updating Approval Workflow policies, and editing or removing other project members.
-- **Viewer**: Read-only access to all resources within the project. Viewers cannot create, edit, or delete any resources.
+- **Viewer**: Read-only access to all resources within the project. Viewers can't create, edit, or delete any resources.
- **No Access**: No permissions within the project. This role is useful when combined with [Additional Privileges](/documentation/platform/access-controls/additional-privileges) to grant scoped access to specific environments or secret paths.
![Project roles](/images/platform/access-controls/project-roles.png)
diff --git a/docs/documentation/platform/email-domain.mdx b/docs/documentation/platform/email-domain.mdx
index ea605093cf..eacea014cb 100644
--- a/docs/documentation/platform/email-domain.mdx
+++ b/docs/documentation/platform/email-domain.mdx
@@ -5,7 +5,7 @@ description: "Learn how to verify your organization's email domains for secure S
<Info>
Email Domain Verification is a paid feature. If you're using Infisical Cloud,
- then it is available under the **Pro Tier**. If you're self-hosting Infisical,
+ then it's available under the **Pro Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase an enterprise license
to use it.
</Info>
@@ -57,12 +57,12 @@ The verification code expires after **7 days**. You must complete verification w
![Add Domain Modal](/images/platform/email-domain/add-domain-modal.png)
- Click **Add Domain** to create the verification request.
+ Select **Add Domain** to create the verification request.
</Step>
<Step title="Copy DNS Verification Details">
- After adding the domain, click the **eye icon** (View details & Verify) on the pending domain row.
+ After adding the domain, select **Verify Domain** on the pending domain row.
A modal will show you the DNS TXT record details:
- **Record Name** — The DNS hostname to add the TXT record to.
@@ -92,9 +92,9 @@ The verification code expires after **7 days**. You must complete verification w
</Step>
<Step title="Verify the Domain">
- Return to the Infisical Email Domains section and click **View details & Verify** on the pending domain.
+ Return to the Infisical Email Domains section and select **Verify Domain** on the pending domain row.
- Click the **Verify Domain** button. Infisical will perform a DNS TXT lookup to confirm the record exists and matches.
+ In the modal that opens, select **Verify Domain**. Infisical will perform a DNS TXT lookup to confirm the record exists and matches.
Once verified, the domain status changes to **Verified** and it's exclusively linked to your organization.
@@ -136,7 +136,7 @@ Email domains are verified at the exact domain level:
Each domain can only be verified by **one organization** across the entire Infisical instance:
-- If Organization A verifies `company.com`, Organization B cannot verify or claim the same domain.
+- If Organization A verifies `company.com`, Organization B can't verify or claim the same domain.
- This prevents cross-organization user provisioning attacks where a malicious org could claim users by email domain.
## SCIM integration
@@ -144,14 +144,14 @@ Each domain can only be verified by **one organization** across the entire Infis
When [SCIM provisioning](/documentation/platform/scim/overview) is enabled, email domain verification is **required**:
- SCIM `POST /Users` requests are validated against the organization's verified domains.
-- If the user's email domain is not verified by the SCIM token's organization, the request is rejected.
+- If the user's email domain isn't verified by the SCIM token's organization, the request is rejected.
- SCIM `PATCH` and `PUT` operations that change a user's email are blocked — email is treated as an immutable identifier.
## FAQ
<AccordionGroup>
<Accordion title="What happens if DNS verification fails?">
- If the DNS TXT record is not found or doesn't match, verification will fail with an error message.
+ If the DNS TXT record isn't found or doesn't match, verification will fail with an error message.
Common causes include DNS propagation delays (wait and retry), incorrect record name (some providers
auto-append the domain), or extra whitespace/quotes in the record value.
</Accordion>
@@ -180,6 +180,6 @@ When [SCIM provisioning](/documentation/platform/scim/overview) is enabled, emai
<Accordion title="Does verifying a parent domain cover all subdomains?">
No. Each subdomain must be verified independently. Verifying `company.com`
- does not automatically cover `app.company.com` or `dev.company.com`.
+ doesn't automatically cover `app.company.com` or `dev.company.com`.
</Accordion>
</AccordionGroup>
diff --git a/docs/documentation/platform/groups.mdx b/docs/documentation/platform/groups.mdx
index 0b1011ed71..ff08df66df 100644
--- a/docs/documentation/platform/groups.mdx
+++ b/docs/documentation/platform/groups.mdx
@@ -4,7 +4,7 @@ description: "Manage groups containing users and machine identities in Infisical
---
<Info>
- Groups is a paid feature. If you're using Infisical Cloud, then it is
+ Groups is a paid feature. If you're using Infisical Cloud, then it's
available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase an enterprise license
to use it.
@@ -18,8 +18,8 @@ Groups have the following properties:
- If a group is added to a project under specific role(s), all identities in the group will be provisioned access to the project with the role(s). Conversely, if a group is removed from a project, all identities in the group will lose access to the project.
- If an identity is added to a group, they will inherit the access control properties of the group including access to project(s) under the role(s) assigned to the group. Conversely, if an identity is removed from a group, they will lose access to project(s) that the group has access to.
-- If an identity was previously added to a project under a role and is later added to a group that has access to the same project under a different role, then the identity will now have access to the project under the composite permissions of the two roles. If the group is subsequently removed from the project, the identity will not lose access to the project as they were previously added to the project separately.
-- An identity can be part of multiple groups. If an identity is part of multiple groups, they will inherit the composite permissions of all the groups that they are part of.
+- If an identity was previously added to a project under a role and is later added to a group that has access to the same project under a different role, then the identity will now have access to the project under the composite permissions of the two roles. If the group is subsequently removed from the project, the identity retains the access granted by its direct project role.
+- An identity can be part of multiple groups and inherits the combined permissions of those groups.
## Workflow
diff --git a/docs/documentation/platform/ldap/general.mdx b/docs/documentation/platform/ldap/general.mdx
index 254db3c8b2..4de6376b13 100644
--- a/docs/documentation/platform/ldap/general.mdx
+++ b/docs/documentation/platform/ldap/general.mdx
@@ -9,7 +9,7 @@ description: "Learn how to log in to Infisical with LDAP."
</Note>
<Info>
- LDAP is a paid feature. If you're using Infisical Cloud, then it is available
+ LDAP is a paid feature. If you're using Infisical Cloud, then it's available
under the **Enterprise Tier**. If you're self-hosting Infisical, then you
should contact [email protected] to purchase an enterprise license to use
it.
@@ -23,9 +23,9 @@ Prerequisites:
<Steps>
<Step title="Prepare the LDAP configuration in Infisical">
- In Infisical, head to **SSO & Provisioning** and select the **SSO** tab. Select **Add Provider**, then choose **LDAP** in the **Add Identity Provider** modal.
+ In Infisical, head to **SSO & Provisioning** and select the **SSO** tab. Select **Add Provider**, choose **LDAP** in the **Add Identity Provider** modal, then select **Continue** to open the **Manage LDAP Configuration** form.
- Input your LDAP server settings in the **Manage LDAP Configuration** form.
+ Input your LDAP server settings.
![LDAP configuration](/images/platform/ldap/ldap-config.png)
@@ -59,7 +59,7 @@ Prerequisites:
![LDAP group mappings section](/images/platform/ldap/ldap-group-mappings-section.png)
- Group mappings ensure that users who log into Infisical via LDAP are added to or removed from the Infisical group(s) that corresponds to the LDAP group(s) they are a member of.
+ Group mappings ensure that users who log into Infisical via LDAP are added to or removed from the Infisical group(s) that corresponds to the LDAP group(s) they're a member of.
![LDAP group mappings table](/images/platform/ldap/ldap-group-mappings-table.png)
diff --git a/docs/documentation/platform/ldap/jumpcloud.mdx b/docs/documentation/platform/ldap/jumpcloud.mdx
index 4a89dad06c..fb8bf981b0 100644
--- a/docs/documentation/platform/ldap/jumpcloud.mdx
+++ b/docs/documentation/platform/ldap/jumpcloud.mdx
@@ -9,7 +9,7 @@ description: "Learn how to configure JumpCloud LDAP for authenticating into Infi
</Note>
<Info>
- LDAP is a paid feature. If you're using Infisical Cloud, then it is available
+ LDAP is a paid feature. If you're using Infisical Cloud, then it's available
under the **Enterprise Tier**. If you're self-hosting Infisical, then you
should contact [email protected] to purchase an enterprise license to use
it.
@@ -32,9 +32,9 @@ Prerequisites:
![LDAP JumpCloud](/images/platform/ldap/jumpcloud/ldap-jumpcloud-enable-bind-dn.png)
</Step>
<Step title="Prepare the LDAP configuration in Infisical">
- In Infisical, head to **SSO & Provisioning** and select the **SSO** tab. Select **Add Provider**, then choose **LDAP** in the **Add Identity Provider** modal.
+ In Infisical, head to **SSO & Provisioning** and select the **SSO** tab. Select **Add Provider**, choose **LDAP** in the **Add Identity Provider** modal, then select **Continue** to open the **Manage LDAP Configuration** form.
- Input your JumpCloud LDAP server settings in the **Manage LDAP Configuration** form.
+ Input your JumpCloud LDAP server settings.
![LDAP configuration](/images/platform/ldap/ldap-config.png)
@@ -69,7 +69,7 @@ Prerequisites:
![LDAP group mappings section](/images/platform/ldap/ldap-group-mappings-section.png)
- Group mappings ensure that users who log into Infisical via LDAP are added to or removed from the Infisical group(s) that corresponds to the LDAP group(s) they are a member of.
+ Group mappings ensure that users who log into Infisical via LDAP are added to or removed from the Infisical group(s) that corresponds to the LDAP group(s) they're a member of.
![LDAP group mappings table](/images/platform/ldap/ldap-group-mappings-table.png)
diff --git a/docs/documentation/platform/scim/azure.mdx b/docs/documentation/platform/scim/azure.mdx
index c0922288c7..0c1b5696ee 100644
--- a/docs/documentation/platform/scim/azure.mdx
+++ b/docs/documentation/platform/scim/azure.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure SCIM provisioning with Azure for Infisical.
<Info>
Azure SCIM provisioning is a paid feature.
- If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
+ If you're using Infisical Cloud, then it's available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase an enterprise license to use it.
</Info>
@@ -46,7 +46,7 @@ Prerequisites:
- Tenant URL: Input the SCIM URL from Step 1 with `?aadOptscim062020` appended as a query parameter.
- Secret Token: Input the **New SCIM Token** from Step 1.
- Afterwards, click **Enable SCIM** and press the **Test Connection** button to check that SCIM is configured properly.
+ Afterwards, select **Enable SCIM**, then select **Test Connection** to check that SCIM is configured properly.
![SCIM Azure](/images/platform/scim/azure/scim-azure-config.png)
@@ -76,6 +76,6 @@ Prerequisites:
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
Infisical's SCIM implementation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
- For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
+ For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers can't and won't have access to the decryption key needed to decrypt your secrets.
</Accordion>
</AccordionGroup>
diff --git a/docs/documentation/platform/scim/jumpcloud.mdx b/docs/documentation/platform/scim/jumpcloud.mdx
index 8ec2df897e..48e20246aa 100644
--- a/docs/documentation/platform/scim/jumpcloud.mdx
+++ b/docs/documentation/platform/scim/jumpcloud.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure SCIM provisioning with JumpCloud for Infisi
<Info>
JumpCloud SCIM provisioning is a paid feature.
- If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
+ If you're using Infisical Cloud, then it's available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase an enterprise license to use it.
</Info>
@@ -59,6 +59,6 @@ Prerequisites:
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
Infisical's SCIM implementation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
- For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
+ For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers can't and won't have access to the decryption key needed to decrypt your secrets.
</Accordion>
-</AccordionGroup>
\ No newline at end of file
+</AccordionGroup>
diff --git a/docs/documentation/platform/scim/okta.mdx b/docs/documentation/platform/scim/okta.mdx
index ed208fba8f..70577a405f 100644
--- a/docs/documentation/platform/scim/okta.mdx
+++ b/docs/documentation/platform/scim/okta.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure SCIM provisioning with Okta for Infisical."
<Info>
Okta SCIM provisioning is a paid feature.
- If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
+ If you're using Infisical Cloud, then it's available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase an enterprise license to use it.
</Info>
@@ -65,6 +65,6 @@ Prerequisites:
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
Infisical's SCIM implementation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
- For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
+ For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers can't and won't have access to the decryption key needed to decrypt your secrets.
</Accordion>
-</AccordionGroup>
\ No newline at end of file
+</AccordionGroup>
diff --git a/docs/documentation/platform/scim/pingfederate.mdx b/docs/documentation/platform/scim/pingfederate.mdx
index ecba1e7eaa..627934fb40 100644
--- a/docs/documentation/platform/scim/pingfederate.mdx
+++ b/docs/documentation/platform/scim/pingfederate.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure SCIM provisioning with PingFederate for Inf
<Info>
PingFederate SCIM provisioning is a paid feature.
- If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
+ If you're using Infisical Cloud, then it's available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase a self-hosted license to use it.
</Info>
@@ -73,7 +73,7 @@ Prerequisites:
<Step title="Configure the Provisioner Data Store">
PingFederate persists provisioning state (last-sync timestamps, externalId mappings, etc.) in a dedicated database.
This is **separate** from your user source — it's PingFederate's internal bookkeeping. The provisioner data store
- must be a JDBC database; LDAP data stores cannot be used for this purpose.
+ must be a JDBC database; LDAP data stores can't be used for this purpose.
1. Create an empty schema in your RDBMS for PingFederate's provisioner state.
2. Run the schema script that matches your RDBMS against that schema. The scripts ship with PingFederate and live at `<pf-install>/server/default/conf/provisioner/sql-scripts/`:
@@ -143,13 +143,13 @@ Prerequisites:
![SCIM create token](/images/platform/scim/scim-create-token.png)
Copy the **SCIM URL** and **New SCIM Token** — you'll paste them into PingFederate's SP Connection in a later step.
- The token is shown once and cannot be retrieved again.
+ The token is shown once and can't be retrieved again.
![SCIM copy token](/images/platform/scim/scim-copy-token.png)
</Step>
<Step title="Create the SP Connection">
- Navigate to **Applications → Integration → SP Connections** and click **Create Connection**.
+ Navigate to **Applications → Integration → SP Connections** and select **Create Connection**.
![Sp connections tab](/images/platform/scim/pingfederate/connection-step-1.png)
@@ -220,7 +220,7 @@ Prerequisites:
</Step>
<Step title="Configure the SCIM channel">
- On the Manage Channels tab, click **Create**. This opens the per-channel wizard with six tabs.
+ On the **Manage Channels** tab, select **Create**. This opens the per-channel wizard with six tabs.
![create channel](/images/platform/scim/pingfederate/channel-step-1.png)
@@ -303,7 +303,7 @@ Prerequisites:
| `givenName` | `user` | `givenName` | `inetOrgPerson` | `givenName` |
| `familyName` | `user` | `sn` | `person` | `sn` |
- For each row: click **Edit** → pick **Root Object Class** → pick **Attribute** → click **Add Attribute** → click **Done**.
+ For each row, select **Edit**, choose **Root Object Class** and **Attribute**, then select **Add Attribute** and **Done**.
`active` doesn't need an explicit mapping — PingFederate derives it from the Account Status Attribute settings in Source Settings.
@@ -332,7 +332,7 @@ Prerequisites:
![channel done](/images/platform/scim/pingfederate/channel-step-11.png)
- On the parent SP Connection wizard's **Outbound Provisioning** tab, click **Next**.
+ On the parent SP Connection wizard's **Outbound Provisioning** tab, select **Next**.
![connection next](/images/platform/scim/pingfederate/connection-step-7.png)
diff --git a/docs/documentation/platform/scim/pingone.mdx b/docs/documentation/platform/scim/pingone.mdx
index 272d8a5b95..cd81dcb12f 100644
--- a/docs/documentation/platform/scim/pingone.mdx
+++ b/docs/documentation/platform/scim/pingone.mdx
@@ -6,7 +6,7 @@ description: "Learn how to configure SCIM provisioning with PingOne for Infisica
<Info>
PingOne SCIM provisioning is a paid feature.
- If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
+ If you're using Infisical Cloud, then it's available under the **Enterprise Tier**. If you're self-hosting Infisical,
then you should contact [email protected] to purchase a self-hosted license to use it.
</Info>
@@ -144,6 +144,6 @@ Prerequisites:
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
Infisical's SCIM implementation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
- For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
+ For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers can't and won't have access to the decryption key needed to decrypt your secrets.
</Accordion>
</AccordionGroup>
diff --git a/docs/images/platform/access-controls/add-metadata-step1.png b/docs/images/platform/access-controls/add-metadata-step1.png
index d72fc9e3a9..f782fb1183 100644
Binary files a/docs/images/platform/access-controls/add-metadata-step1.png and b/docs/images/platform/access-controls/add-metadata-step1.png differ
diff --git a/docs/images/platform/access-controls/add-metadata-step2.png b/docs/images/platform/access-controls/add-metadata-step2.png
index fce093a967..fa94edb594 100644
Binary files a/docs/images/platform/access-controls/add-metadata-step2.png and b/docs/images/platform/access-controls/add-metadata-step2.png differ
diff --git a/docs/images/platform/access-controls/add-metadata-step3.png b/docs/images/platform/access-controls/add-metadata-step3.png
index fce093a967..ad5775242e 100644
Binary files a/docs/images/platform/access-controls/add-metadata-step3.png and b/docs/images/platform/access-controls/add-metadata-step3.png differ
diff --git a/docs/images/platform/access-controls/temporary-access.png b/docs/images/platform/access-controls/temporary-access.png
index 7428c21ccd..e4e93dbfde 100644
Binary files a/docs/images/platform/access-controls/temporary-access.png and b/docs/images/platform/access-controls/temporary-access.png differ
diff --git a/docs/images/platform/project-access-requests/request-access.png b/docs/images/platform/project-access-requests/request-access.png
index e118135aaa..4c19010128 100644
Binary files a/docs/images/platform/project-access-requests/request-access.png and b/docs/images/platform/project-access-requests/request-access.png differ