Skip to main content

Organisation vs Team in Dapple: What's the Difference?

An Organisation and a Team are different concepts and it's important to know the difference

Written by Oz Osbaldeston

An Organisation in Dapple is your top-level workspace — the umbrella for everything. A Team is a smaller group inside an Organisation, with its own users and permissions. Most organisations have one Organisation and several Teams (e.g. Editorial, Operations, Programmes). You can be a member of multiple Teams inside the same Organisation, but each Team's permissions are independent.

Quick comparison

Organisation

Team

What it is

Your top-level workspace — your business or programme as a whole

A smaller group of users inside an Organisation

What it holds

Projects, Teams, Users, settings, billing

A subset of users with specific permissions and project access

Permissions

Set at the Organisation level (Admin / Member / Reviewer)

Set at the Team level — which projects this team can see

How many you can have

Multiple, each billed separately

Multiple per Organisation, no extra cost

Example

'The Melville Gallery'

'Curatorial Team', 'Review Team', 'Press Team'

When should I create another Team?

  • You run distinct programmes that shouldn't see each other's submissions (e.g. literary magazine vs visual arts award).

  • You want different staff to manage different projects without overlap.

  • External reviewers should only see specific projects, not everything.

  • You want to delegate management of certain programmes without giving full admin access.

When should I create another Organisation instead?

  • You're running a completely separate brand or business entity.

  • Billing must be tracked totally separately.

  • The two operations need different organisation-wide settings (logo, sender email, country).

  • Visibility separation needs to be absolute — even admin users shouldn't see across the boundary.

Can I be in multiple Teams?

Yes. You can be a member of as many Teams as needed within an Organisation. Each Team's permissions apply independently — being an Admin in one Team doesn't make you an Admin in another. Useful for organisations where staff wear multiple hats.

How does this affect creators?

Creators don't see your internal structure. From their side, they submit to a Project — your Organisation's branding shows up on the Page and confirmation email, but Teams are invisible. Teams are purely an internal way to organise your staff.

Where to go next

Did this answer your question?