mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-20 11:45:50 +00:00
clean up doc migration
This commit is contained in:
@@ -1,3 +0,0 @@
|
||||
{% admonition type="info" name="Attention" %}
|
||||
Permission delegation functionality is part of the proposed XLS-75d extension to the XRP Ledger protocol. You can use these functions on test networks for now. Until there is an amendment in a stable release, the details documented on these pages are subject to change.
|
||||
{% /admonition %}
|
||||
@@ -4,13 +4,13 @@ seo:
|
||||
labels:
|
||||
- Accounts
|
||||
- Permissions
|
||||
status: not_enabled
|
||||
---
|
||||
# Permission Delegation
|
||||
|
||||
{% partial file="../../_snippets/permission-delegation-disclaimer.md" /%}
|
||||
|
||||
XRPL accounts can delegate both transaction permissions and granular permissions to other accounts, enhancing flexibility and enabling use cases such as implementing role-based access control. This delegation is managed using the [`DelegateSet`](../../references/protocol/transactions/types/delegateset.md) transaction.
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%})_
|
||||
|
||||
## Assigning Permissions
|
||||
|
||||
You can assign permissions to another account by submitting a `DelegateSet` transaction.
|
||||
@@ -103,4 +103,6 @@ Any other errors are the same as when the _rDelegatingAccount_ sends transaction
|
||||
* Delegating permissions grants significant control. Ensure you trust the delegated account.
|
||||
* The account specified in the `Delegate` field is responsible for paying the transaction fee.
|
||||
* A delegated account can only perform actions that have been explicitly permitted.
|
||||
{% /admonition %}
|
||||
{% /admonition %}
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
@@ -5,14 +5,14 @@ labels:
|
||||
- Accounts
|
||||
- Permissions
|
||||
- Delegate
|
||||
status: not_enabled
|
||||
---
|
||||
|
||||
# DelegateSet
|
||||
|
||||
{% partial file="../../../../_snippets/permission-delegation-disclaimer.md" /%}
|
||||
|
||||
The `DelegateSet` transaction creates, modifies, or deletes a `Delegate` ledger object, thereby granting, changing, or revoking delegated permissions between accounts.
|
||||
|
||||
_(Requires the [PermissionDelegation amendment][] {% not-enabled /%})_
|
||||
|
||||
## Example `DelegateSet` JSON
|
||||
|
||||
```json
|
||||
@@ -142,3 +142,4 @@ The transactions disabled for delegation include: `AccountSet`, `RegularKeySet`,
|
||||
|
||||
- If the Account does not have enough balance to meet the reserve requirement, (because `DelegateSet` will create a ledger object `ltDELEGATE`, whose owner is `Account`), return `tecINSUFFICIENT_RESERVE`.
|
||||
|
||||
{% raw-partial file="/docs/_snippets/common-links.md" /%}
|
||||
|
||||
Reference in New Issue
Block a user