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

docs: add new secret actions to permission doc

Browse Source
This commit is contained in:
Daniel Hougaard
2025-03-28 00:01:47 +04:00
parent 8f49d45309
commit 5cdabd3e61
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/internals/permissions/project-permissions.mdx
View File

@@ -140,12 +140,14 @@ Below is a comprehensive list of all available project-level subjects and their
#### Subject: `secrets` #### Subject: `secrets`
Supports conditions and permission inversion Supports conditions and permission inversion
| Action | Description | | Action | Description | Notes |
| -------- | ------------------------------- | | -------- | ------------------------------- | ----- |
| `read` | View secrets and their values | | `read` | View secrets and their values | This action is the equivalent of granting both `describeSecret` and `readValue`. The `read` action is considered **legacy**. You should use the `describeSecret` and/or `readValue` actions instead. |
| `create` | Add new secrets to the project | | `describeSecret` | View secret details such as key, path, metadata, tags, and more | If you are using the API, you can pass `viewSecretValue: false` to the API call to retrieve secrets without their values. |
| `edit` | Modify existing secret values | | `readValue` | View the value of a secret.| In order to read secret values, the `describeSecret` action must also be granted. |
| `delete` | Remove secrets from the project | | `create` | Add new secrets to the project | |
| `edit` | Modify existing secret values | |
| `delete` | Remove secrets from the project | |
#### Subject: `secret-folders` #### Subject: `secret-folders`