Production is locked until a market agreement is recorded

Team

Who can act on behalf of Bissau Foods. Roles are coarse on purpose: a role nobody can explain is a role nobody revokes.

10 active1 invited

Members

Who is on the account

  • Ana Paula Mendesana.mendes@bissaufoods.exampleowner
  • Teresa Kialateresa.kiala@bissaufoods.exampledeveloper
  • Celso Macuácuacelso.macuacua@bissaufoods.examplefinance
  • Ivone Fernandesivone.fernandes@bissaufoods.exampleread-only
  • Sandrine Mendessandrine.mendes@bissaufoods.exampleowner
  • Nuria Vaznuria.vaz@bissaufoods.exampledeveloper
  • Mariana Chissanomariana.chissano@bissaufoods.examplefinance
  • Luzia Ndalaluzia.ndala@bissaufoods.exampleread-only
  • Yara Delgadoyara.delgado@bissaufoods.exampleowner
  • Carla Pirescarla.pires@bissaufoods.exampledeveloper
  • Teresa Barrosteresa.barros@bissaufoods.examplefinance

Invite

Add someone

Keys, webhooks, sandbox and the request log.

Roles

What each role may do

Roles and permissions
RoleCan doKeysInvoices
ownerEverything, including billing and the market agreement.create, rotate, revokeread, download
developerKeys, webhooks, sandbox and the request log.create, rotate, revokeno
financeInvoices, receipts and B2B orders. No keys.noread, download
read-onlyRead the dashboard, usage and the status page.nono

Audit

Everything a member does is recorded

Who created a key, who rotated a secret, who downloaded an invoice. The log is readable by owners and by anyone you give the read-only role.

Keys are attributed to the member who created them, and a revoked member's keys keep working until someone revokes them too — a person leaving must never take an integration down by accident. Look for actor.member_id in the request log. Open the request log