Users, memberships and roles
Our platform has two top level objects:
- A user represents you. Everything related to your individual profile is stored here.
- An organisation represents your company. All objects on the platform except users are nested under your organisation.
Your user is linked to your organisation by a membership. This membership defines your roles within the organisation.
Users
A user represents an individual person using the Griffin platform. You can become a user by:
- registering for the sandbox
- accepting an invitation from an existing user
Memberships
A membership represents a relationship between a user and an organisation. All users have at least one membership.
- If you register for the sandbox, we automatically create a new organisation of which you are a member.
- If you accept an invitation from an existing user, you become a member of that user’s organisation.
You can be a member of many organisations. Choose the organisation you want to interact with by:
- selecting it from the organisation dropdown menu in the app.
- using an API key associated with that organisation.
Roles
A role represents a pre-defined set of actions you can take within an organisation. Your role(s) in each organisation are defined in your membership. This means you can have different roles in different organisations.
- If you register for the sandbox, you automatically have the Team admin, Payments and Compliance roles.
- If you accept an invitation from an existing user, you will be a Team member by default until a Team admin updates your roles. Team members cannot perform any actions.
| Role | Actions |
|---|---|
| Compliance | - Create and submit applications for reliance onboarding - Add and remove members of pooled accounts - Accept and reject customer applications - Create customer applications |
| Team admin | - Add and remove users - Edit user roles - Create, edit and delete webhooks |
| Payments | - Open and close bank accounts - Make payments from accounts |
| Team member | - No actions |