awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove outdated documentation files: deleted usage, REST API, and platform guides to streamline content and improve clarity.

Browse Source
This commit is contained in:
Victor Santos
2025-11-10 21:15:50 -03:00
parent d9ef0b23d1
commit 9f389081fb
41 changed files with 50 additions and 462 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/documentation/guides/nextjs-vercel.mdx
View File

@@ -199,7 +199,7 @@ Next, navigate to your project's integrations tab in Infisical and press on the
Opting in for the Infisical-Vercel integration will break end-to-end encryption since Infisical will be able to read
your secrets. This is, however, necessary for Infisical to sync the secrets to Vercel.
Your secrets remain encrypted at rest following our [security guide mechanics](/security/mechanics).
Your secrets remain encrypted at rest following our [security guide mechanics](/internals/security).
</Note>
Now select **Production** for (the source) **Environment** and sync it to the **Production Environment** of the (target) application in Vercel.
@@ -238,7 +238,7 @@ At this stage, you know how to use the Infisical-Vercel integration to sync prod
<Accordion title="Is opting out of end-to-end encryption for the Infisical-Vercel integration safe?">
Yes. Your secrets are still encrypted at rest. To note, most secret managers actually don't support end-to-end encryption.
Check out the [security guide](/security/overview).
Check out the [security guide](/internals/security).
</Accordion>
</AccordionGroup>

2
docs/documentation/guides/organization-structure.mdx
View File

@@ -75,7 +75,7 @@ Infisical’s access control framework is unified for both human users and machi
### 7.3 Attribute-Based Access Control (ABAC)
[Attribute-based Access Controls](/documentation/platform/access-controls/attribute-based-access-controls) allow restrictions based on tags or attributes linked to secrets. These can be integrated with SAML assertions and other security frameworks for dynamic access management.
[Attribute-based Access Controls](/documentation/platform/access-controls/abac/overview) allow restrictions based on tags or attributes linked to secrets. These can be integrated with SAML assertions and other security frameworks for dynamic access management.
### 7.4 User Groups