Partner pages and controls

Open the workspace walkthrough.

How to use this reference

Find the page name or application location below. Open the saved object in your workspace, then use its action or settings surface. Object identifiers in a route are replaced by the selected record.

Controls depend on the current entity, wallet, network, feature access, and object state. A route or action entry does not grant permission or establish that a transaction will succeed.

Settings

Application location: /partners/settings

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Edit public profile

Application location: /partners/public-profile/edit

This route requires the relevant capability to be enabled for the current organization.

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Public profile

Application location: /partners/public-profile

This route requires the relevant capability to be enabled for the current organization.

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Create integration

Application location: /partners/integrations/add

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Edit integration

Application location: /partners/integrations/:experienceId/edit

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Incident protection

Application location: /partners/incident-protection

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

Audit

Application location: /partners/audit

This route requires the relevant capability to be enabled for the current organization.

Operating surfaces: Examination access.

Action reference

organizationAuditExaminationGrantCreate

• Required inputs: namespace, workspace, organizationId, expectedActorKey, requestId, email, username, durationSeconds.
• Permitted role families: asset_manager, asset_issuer, nav_reporter, reseller. Current scope and preconditions are checked at execution.

organizationAuditExaminationGrantRevoke

• Required inputs: namespace, workspace, organizationId, expectedActorKey, grantId.
• Permitted role families: asset_manager, asset_issuer, nav_reporter, reseller. Current scope and preconditions are checked at execution.

Programs

Application location: /partners

Operating surfaces: programs.manager; channels.inventory; wrappers.inventory.

Action reference

partnerManagerBootstrap

• Required inputs: kind, vaultAddress, currentResellerManager, minPartnerSplitBps.
• Permitted role families: curator, vault_manager. Current scope and preconditions are checked at execution.

partnerSubmitApplication

• Required inputs: kind, managerAddress, partnerAddress, metadataHash.
• Permitted role families: partner. Current scope and preconditions are checked at execution.

partnerChannelDeploy

• Required inputs: kind, managerAddress, partnerAddress, payoutRecipient, partnerSplitBps, name, symbol, mode.
• Permitted role families: partner, curator, vault_manager. Current scope and preconditions are checked at execution.

partnerChannelBlockedUpdate

• Required inputs: kind, managerAddress, partnerAddress, wrapperAddress, blocked.
• Permitted role families: curator. Current scope and preconditions are checked at execution.

partnerFeeSharesClaim

• Required inputs: kind, managerAddress, recipient.
• Permitted role families: partner. Current scope and preconditions are checked at execution.

partnerBorrowerFeeClaim

• Required inputs: kind, managerAddress, assets, recipient.
• Permitted role families: curator. Current scope and preconditions are checked at execution.

partnerApplicationReview

• Required inputs: kind, managerAddress, partnerAddress, decision, payoutRecipient, partnerSplitBps.
• Permitted role families: vault_owner. Current scope and preconditions are checked at execution.

partnerChannelTermsUpdate

• Required inputs: kind, managerAddress, partnerAddress, wrapperAddress, payoutRecipient, partnerSplitBps.
• Permitted role families: vault_owner. Current scope and preconditions are checked at execution.

partnerManagerFeeAttribution

• Required inputs: kind, managerAddress, mode, assets, curatorRecipient.
• Permitted role families: vault_owner. Current scope and preconditions are checked at execution.

partnerWrapperDeposit

• Required inputs: kind, wrapperAddress, vaultAddress, shareClass, assetAddress, assets, receiver.
• Permitted role families: lender, partner. Current scope and preconditions are checked at execution.

partnerWrapperRedeem

• Required inputs: kind, wrapperAddress, vaultAddress, shareClass, shares, receiver.
• Permitted role families: lender, partner. Current scope and preconditions are checked at execution.

partnerWrapperTransfer

• Required inputs: kind, wrapperAddress, vaultAddress, shareClass, shares, receiver.
• Permitted role families: lender, partner. Current scope and preconditions are checked at execution.

Authority & recovery

Application location: /partners/settings/authority

Use the page's displayed inventory, status, and supported row actions. The current registry does not declare a separate form-control mapping for this route; do not infer an editable field from a read-only value.

builder controls

Input surface: partner.earn_integration::builder.

Complete the task

Review the object and active inputs. Use Workspace Update where the action requires it, complete the permitted approval or signing sequence, and verify the saved record after reload. Check Troubleshooting for stale, pending, or blocked actions.