Block · Teams and access

Organisations and teams

Adds organisations, teams, memberships with roles and email invitations, private to the members of each organisation: Postgres row-level security shows a person only the organisations they belong to and everything in them. Whoever creates an organisation becomes its owner; owners and admins invite people by email, create teams and change roles. An invited person who already has an account joins straight away; anyone else gets an email and joins when they sign up with that address. Optionally makes one of your tables (projects, accounts) belong to an organisation, private to its members too.

View the files

use_template { slug: "organisations-and-teams" } adds

Tables: organisation, team, membership, invitation
Fields: ‹attach_to›.organisation_id
Components: OrganisationConsole
Pages: /organisations, /organisations/:id, /organisations-admin
Workflows: organisation-owner, invitation-send, invitation-join
Rules: 1 on organisation, 1 on team, 2 on membership, 1 on invitation

What it adds to your app

Tables organisation, team, membership and invitation. Organisations list and an organisation console (members, roles, teams, invites). A staff overview of every organisation. Workflows: owner membership, invite or add by email, join on signup.

Tables

organisation name, about, website, owner_id
team organisation_id, name, description
membership organisation_id, member_id, team_id, role, status
invitation organisation_id, email, role, team_id, status, invited_by

Fields added to your tables

‹attach_to›.organisation_id

Workflows

organisation-owner Make the creator the organisation's owner. On organisation created
invitation-send Add or email the person invited. On invitation created
invitation-join Add new signups to the organisations that invited them. On ‹member_role› created

Components

OrganisationConsole One organisation: members with roles, teams, and invitations, managed by its owner and admins

Rules on every write

organisation Give the organisation a name of 2 to 80 characters.
team Only the organisation's owner or admins can do that.
membership Only the organisation's owner or admins can do that.
membership A membership stays with its person and organisation.
invitation Only the organisation's owner or admins can do that.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`member_role`	The role whose people create and join organisations (their own table holds the members). Optional.	`member`
`email_field`	Optional: the email field on that role's table, used to match invitations to people. Optional.	`email`
`attach_to`	Optional: a table of yours (projects, accounts) whose rows then belong to an organisation: it gets organisation_id, and that role sees and changes only its organisations' rows. Optional.	`project`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Prompt

Add the Organisations and teams template (slug "organisations-and-teams") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (member_role: who joins organisations; email_field: their email field; attach_to: records that belong to an organisation).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "organisations-and-teams",
    "project_id": "<your project id>",
    "params": {
      "member_role": "member",
      "email_field": "email",
      "attach_to": "project"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use organisations-and-teams --param member_role=member --param email_field=email --param attach_to=project --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Block · Teams and access

Organisations and teams

View the files

use_template { slug: "organisations-and-teams" } adds

Tables: organisation, team, membership, invitation
Fields: ‹attach_to›.organisation_id
Components: OrganisationConsole
Pages: /organisations, /organisations/:id, /organisations-admin
Workflows: organisation-owner, invitation-send, invitation-join
Rules: 1 on organisation, 1 on team, 2 on membership, 1 on invitation

What it adds to your app

Tables

organisation name, about, website, owner_id
team organisation_id, name, description
membership organisation_id, member_id, team_id, role, status
invitation organisation_id, email, role, team_id, status, invited_by

Fields added to your tables

‹attach_to›.organisation_id

Workflows

organisation-owner Make the creator the organisation's owner. On organisation created
invitation-send Add or email the person invited. On invitation created
invitation-join Add new signups to the organisations that invited them. On ‹member_role› created

Components

OrganisationConsole One organisation: members with roles, teams, and invitations, managed by its owner and admins

Rules on every write

organisation Give the organisation a name of 2 to 80 characters.
team Only the organisation's owner or admins can do that.
membership Only the organisation's owner or admins can do that.
membership A membership stays with its person and organisation.
invitation Only the organisation's owner or admins can do that.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`member_role`	The role whose people create and join organisations (their own table holds the members). Optional.	`member`
`email_field`	Optional: the email field on that role's table, used to match invitations to people. Optional.	`email`
`attach_to`	Optional: a table of yours (projects, accounts) whose rows then belong to an organisation: it gets organisation_id, and that role sees and changes only its organisations' rows. Optional.	`project`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Prompt

Add the Organisations and teams template (slug "organisations-and-teams") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (member_role: who joins organisations; email_field: their email field; attach_to: records that belong to an organisation).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "organisations-and-teams",
    "project_id": "<your project id>",
    "params": {
      "member_role": "member",
      "email_field": "email",
      "attach_to": "project"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use organisations-and-teams --param member_role=member --param email_field=email --param attach_to=project --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Organisations and teams

What it adds to your app

Tables

Fields added to your tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Booking calendar

Stripe subscriptions

Comments

Your agent adds it. Appbricx runs it.

Organisations and teams

What it adds to your app

Tables

Fields added to your tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Booking calendar

Stripe subscriptions

Comments

Your agent adds it. Appbricx runs it.

Organisations and teams

What it adds to your app

Tables

Fields added to your tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

Booking calendar

Stripe subscriptions

Comments

Your agent adds it. Appbricx runs it.

Organisations and teams

What it adds to your app

Tables

Fields added to your tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

Booking calendar

Stripe subscriptions

Comments

Your agent adds it. Appbricx runs it.