Choose the wallet ownership model
A Request is not an unrestricted signing grant. Para checks the policy, its active version, the user’s consent and settings, and any additional approval requirements when signing. An applicable denial still prevents signing.
While Permissions is on, Para denies raw signatures for app-owned and user-owned wallets unless an active policy that applies to the wallet has a rule allowing the
raw_signature action. Raw signatures include sign-raw requests and message signing from wallets that cannot sign as EVM, such as Solana, Stellar, and Sui wallets. The Developer Portal forms cannot create this rule; use JSON authoring.
Permissions supports EVM, Solana, Cosmos, Stellar, and Sui wallets. The Developer Portal forms cover a subset of policy shapes; use JSON authoring or work with Para for other supported configurations. Each policy selects one wallet type and can narrow it to specific networks, and each rule names the actions it governs. Check the policy reference for the facts supported by each request.
Set up your application
Choose an authoring path, then integrate the consent, signing, or approval flows your app needs.Set up permissions
Find the Developer Portal, CLI, and backend guides for your setup.
Add capabilities as you need them
Start with one narrowly scoped policy and test a request inside and outside its boundary. Add nested conditions, spending windows, user-adjustable limits, or conditional approvals when the application needs them. More than one policy can be active; their selectors and effects determine the combined decision, not their position in a list.Read the policy JSON reference
Target wallets and networks, combine conditions, and understand policy evaluation.
Integrate consent and adjustable limits
Request standing access and let users choose declared personal limits.
Integrate conditional approvals
Coordinate authenticated decisions or collect transaction signatures.
Manage permissions from your backend
Manage authorization scopes, assignments, and permitted workflow settings.
Test on beta, then request production review
Beta and production keys have independent policy records. Nothing transfers automatically. Test the intended allowed, reviewed, and denied behavior on beta, then work with Para to review and manually publish the approved production configuration.Manage the policy lifecycle
Understand immutable versions, activation, expiry, and the production review process.