Set up permissions

Choose how to author policies and connect them to your application

Start by creating a policy on a beta API key, called Development in Developer Portal. Then connect the consent, signing, or approval flows your application needs. The setup path depends on the policy you want to create and who owns the wallets.

Authoring defines the rules Para enforces. Client SDKs let authenticated users participate in those rules, while backend methods administer assignments, scopes, and settings the policy permits. Neither client nor backend management methods rewrite the policy definition.

Choose how to create a policy

Use Developer Portal when its forms cover your policy. The forms author policies for EVM, Solana, Cosmos, Stellar, and Sui wallets. For other supported configurations, including nested conditions, adjustable limits, conditional approvals, and raw signature rules, author JSON through the CLI. Both paths validate the policy before it can become active.

Create policies in Developer Portal

Author policies with JSON

Policy JSON reference

Contact Para if you need help designing or checking a policy. Production publication requires Para review; beta policies do not transfer automatically.

Connect permissions to your application

For user-owned wallets, integrate consent and any adjustable settings or approval workflows. For app-owned wallets, enforce policies through server-side signing. Your backend can also manage approval roles, authorization scopes, and declared workflow settings using the server secret; these administration methods are separate from policy authoring.

Integrate consent and adjustable limits

Integrate conditional approvals

Enforce policies on app-owned wallets

Manage permissions from your backend

Test and publish

Test requests that should be allowed, denied, or sent for review before requesting production publication. As your policy changes, create new versions and verify their activation and consent behavior.

Manage the policy lifecycle