Home / Product / Users and groups

Bring people together

Give every person a place—and every team a shared boundary.

Model customers, teammates, organizations, and membership inside the same backend as the work and content they can reach.

See what it changes Technical guide ↗

Users and groups in a product

A person joinsCreate an account for the customer or teammate

Place them in contextConnect them to a team, workspace, or organization

Share the right product experienceRecords and actions follow that membership

People and product data belong together

01Represent real teamsModel membership instead of scattering role checks through code.

02Make ownership usefulConnect people directly to the records and files they own.

03Support tenant-style productsUse groups as the foundation for shared workspaces and organizations.

Why it matters

A team account is more than a login and a role string.

In a collaborative product, people belong to organizations, projects, or workspaces. They create records, share files, invite colleagues, and leave. If membership lives in one service and product data in another, every feature has to reconcile the two.

Daptin keeps accounts, groups, ownership, and relationships in the same application model. A group can represent a team or workspace, while ordinary relationships connect its members to the records they work on.

Permissions, files, actions, and live updates can then use that shared context. The product gains a consistent answer to who this person is and which part of the application they belong to.

Build around organizations

Create team, tenant, or workspace experiences from explicit membership.

Keep ownership attached

A record can know its owner and the groups that share it.

Handle change in one place

Membership changes can affect the product paths that rely on the group.

How it fits

Part of one connected backend.

Users and groups does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Create

A person receives an application account.

Step 2Relate

The account joins a group representing a team or workspace.

Step 3Own

Records and files connect to owners and sharing groups.

Step 4Apply

Permissions and actions use that identity context.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Client portal

Customers see their own requests plus work shared with their organization.

Team workspace

Members collaborate on projects, files, and approvals.

Partner network

Different organizations reach only the records shared with them.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes users and groups more useful.

Know the boundary

What Daptin leaves in your hands.

Groups are flexible building blocks, not a complete organization-management product. You still design invitations, membership approval, offboarding, administrator roles, and the tenant model that fits your application.

Understand the operating responsibility →

Build from one foundation

Make users and groups part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities