Organizations, users, and credentials

Masklabs has three layers, and each one does a different job. Once you see the split, everything in the dashboard falls into place.

Your user account

The email and password you sign in with. It identifies you, not your traffic, a user account never talks to the proxy network directly. One user can belong to several organizations and switch between them from the header.

Organizations

The organization is the wallet. It owns the data balance, the transaction history, and every proxy credential. When anyone in the organization moves traffic, it drains the same shared balance.

You get a personal organization automatically when you sign up, so if you're working alone you never have to think about this layer. Create a separate organization when a team or a project needs its own balance and its own members.

Roles inside an organization:

• Member, full product access: create credentials, watch usage, buy data.
• Admin, everything a member can do, plus invite or remove people, change roles, and rename the organization.
• Owner, everything an admin can do, plus delete the organization.

Proxy credentials

A credential is the username and password your client actually connects with, mlabs_a1f9c3 plus the password shown once at creation. Credentials belong to the organization, not to the person who created them, and they all spend the same shared balance.

Issue one credential per service or machine rather than sharing one everywhere. Each credential reports its own usage line and can carry its own daily or monthly cap, so you can see which job is spending the pool and shut off exactly one thing when it misbehaves, rotate its password, disable it, or delete it without touching the rest.

The mental model

You sign in → pick an organization (the wallet) → its credentials move traffic and drain the shared balance. Billing is per organization, access is per user, traffic is per credential.