Skip to content
Help

Teams, roles and approvals

Add the people and agents you work with, decide what each can do, ask for approval before a payout is sent, and have a second person confirm changes.

Adding people

Everyone signs in with their own wallet. In Settings, Members, an admin or the owner can add someone two ways:

  • By wallet address. They see the workspace the next time they sign in, and open it from the workspace menu at the top of the page.
  • With an invite link. The link works once, for 7 days, for one role. Whoever opens it and signs in joins with the wallet they signed in with. A link not used yet can be withdrawn.

How many people a workspace can have depends on its plan: 5 on Free, 20 on Pro, 200 on Team and 5 on each API plan, the owner included. Adding someone beyond the plan is refused, and nobody already in is ever removed because of a plan. Anyone can leave; the owner cannot be removed.

What each role can do

RoleWhat it can do
OwnerEverything, including deleting the workspace, making or changing admins, and unlocking the last locked month. One per workspace.
AdminMembers and invites, settings and approvals, notification channels, webhooks, API keys, auditor links, the chart of accounts, locking a month, the plan, the Circle Gateway file, accounting software, confirming or rejecting waiting changes, the activity log and downloading all of the workspace’s data, plus everything an operator and an approver can do. Only the owner can make or change an admin.
OperatorPrepares and sends payouts, makes payment links, sends refunds, makes, issues and voids invoices and recurring invoices, imports an address’s history, reads a month on the Close page, books lines to accounts, writes rules and books past lines, names addresses and imports or exports names, saves and keeps recurring payout schedules, downloads files.
ApproverApproves or rejects payouts. Sees the books, payouts, links, invoices, members, plan and settings; the activity log, API keys, webhooks, auditor links, notification channels, invites, waiting changes and the Gateway file are for admins. Cannot download files, apart from a locked month’s report.
ViewerSees what an approver sees. Changes nothing and cannot download files, apart from a locked month’s report.
AgentFor an AI agent or a script with its own wallet. Prepares payouts, checks them and discards its own; every payout it prepares waits for a person’s approval, whatever the workspace’s approval setting, and an operator, an admin or the owner signs it. Sees what a viewer sees. Never sends, approves or changes settings, and cannot keep a recurring payout schedule.

A role is checked on every request, so removing someone takes effect at once, and invite links they made stop working. So do the API keys and auditor links they made, and the webhooks and notification channels they added stop sending, unless whoever removes them chooses to keep these working. The same happens when an admin is made anything less than an admin. A payment link always pays the owner’s wallet, whoever made it.

Approvals before a payout is sent

In Settings, Approvals, choose 1 or 2 approvals, and optionally only for payouts above an amount in USDC or EURC. Then:

  • the person who prepared a payout cannot approve it; a payout an agent prepared needs at least one approval even when the workspace asks for none, and the person who added the agent may give it;
  • an approval is for the payout exactly as it stood; if the payout changes, it must be approved again;
  • a rejection needs a reason, and the payout can never be sent; prepare a new one;
  • approvers get a notification when a payout is waiting for them.

Memoline will not prepare any transaction for a payout that is still waiting. A payout that has already started sending is never stopped halfway. Approvals govern what happens in Memoline: a wallet can always send money outside it, so keep the paying wallet with people you trust.

A second person confirms changes

An admin can turn on "A second person confirms changes" in Settings (it needs two people who can confirm: the owner and an admin, or two admins). While it is on, these wait until an admin or the owner other than the person who asked confirms them in Settings:

  • a name or kind set, changed or removed in the address book, and an address book file (one change for the whole file);
  • an API key made (shown once, refused until confirmed);
  • a webhook endpoint or a notification channel added (sent nothing until confirmed);
  • an auditor link made (it opens nothing until confirmed);
  • a member added, a role changed, or an invite made (the link works once confirmed);
  • the approvals a payout needs, the amounts above which it needs them, and the two-step sign-in requirement.

Each waiting change shows all of what it does before anyone confirms it: every name in an address book file, a key’s budget and the payees it may pay, where an endpoint or a channel sends, and the accounts, the currency and the dates an auditor link shows, and until when it works. The person who asked never confirms their own change. An admin or the owner who asked can withdraw it, and anyone else who can confirm can reject it, with a reason; an operator’s request is ended by an admin or the owner. Rejecting or withdrawing a waiting key revokes it, a waiting endpoint, channel or invite link is turned off, and a waiting auditor link is ended. A change applies only if what it changes is still as it was when asked, and only while the person who asked could still make it (someone removed, or moved to a role that cannot make that change, leaves nothing that can be confirmed); otherwise it is refused, and can be rejected or asked again. A change waits up to 7 days, then ends unapplied, and a key, endpoint, channel, invite or auditor link that waited with it is revoked, turned off or ended. Removing an endpoint, a channel or a member, withdrawing an invite, revoking a key and ending an auditor link never wait. Ending an auditor link that is still waiting also ends its waiting change. Turning the rule off also waits for a second admin, unless the owner does it; changes already waiting keep waiting until someone confirms or rejects them, or they end after 7 days. Only an admin or the owner sees the list of waiting changes. Every request is in the activity log with its old and new values, and every confirmation, rejection, withdrawal and expiry with who decided it.

For this to mean two people, each admin should turn on two-step sign-in: confirming asks for the code only from someone who has turned it on. On the Team plan, an admin can require it of every admin and the owner in Settings, Two-step sign-in.

The activity log

Settings, Activity lists who did what: payouts prepared, approved and rejected, payee checks looked at, links, refunds, members, settings, changes asked and decided, months locked, imports and downloads. Only admins and the owner can open it. Entries are only added, never changed. Each one carries a fingerprint of the one before it, and the newest is recorded with the workspace, so if an entry were changed or removed, the page says so. Only someone able to rewrite the database itself could hide a change. Download it as CSV for an accountant or auditor.

Your data

In Settings, Your data, an admin or the owner can download everything Memoline keeps for the workspace as one file. The owner can then delete the workspace by typing its name. Payments already on Arc stay on Arc; see custody and safety.