Particle CS Launch app (opens in a new tab)

Shared control without a shared key.

Each person gets the access their job needs. Nobody inherits a master key, and you can always see who did what.

Map your team’s rolesHow roles and permissions work
Where control breaks today

Teams share keys because wallets can’t share control.

Most wallets have one kind of holder: whoever has the key. Teams work around that — and the workarounds become the risk.

One seed phrase, many holders

A passed-around seed phrase gives everyone the same unlimited power — and no way to tell who acted.

Co-signing everything slows everyone down

When every action needs several signatures, routine work stalls — and preparing still isn’t separated from approving.

Work that lives in one person’s browser

The rest of the team learns what’s in flight from a message — or from the balance.

People change faster than wallets do

Joining, changing roles and leaving each become a key ceremony, so access changes get postponed.

In practice

Remove someone without touching the funds.

When a teammate leaves, the owner removes their wallet from its role. Nothing else changes.

What you set up

  • A role for each job, with a wallet cap
  • Each person on their own wallet
  • What each role may do, per operation
  • The owner on a separate, protected wallet
Run an account as a team, step by step (opens in a new tab)

Teammate
leaves

Owner removes
their role

Nothing else
changes

Their old
wallet

Refused

Illustrative

The approach

Give each person a role, not a key.

Set on the account, so the same rules apply in the Platform, your own tools or a script.

Each person, their own key

Everyone acts with their own wallet inside their own role. Nobody inherits anyone else’s access.

Grant only what the job needs

Give each role just the steps it needs, for each kind of operation — request, approve, cancel, or none.

One queue for the team

Requests posted on-chain sit in a queue everyone on the account can read: what’s waiting, who asked, and how long is left.

People change; assets stay put

Someone joining or leaving is a role change. The account keeps running and the assets stay where they are.

Before you hand out roles

What the account enforces — and what your team owns.

Shared control is only as good as the roles you assign. We separate the two clearly.

Enforced by the account

  • Which roles exist, and which wallets hold them
  • What each role may do: request, approve, cancel
  • Role changes signed by the owner and recorded on-chain
  • An on-chain record of who did what

Your responsibility

  • Deciding who should hold which role
  • Removing access promptly when people change jobs
  • Key management for every team member
  • Keeping an off-chain record of who holds which address

Give the team its own roles.

Bring one shared account and we’ll map its roles with you. Or set one up in the Platform yourself.

Talk to usBloxchain Platform