Feature
Customer scoping
Brikl customer scoping shows each customer only their own catalogs, pricing and stores, so one platform serves many clients and none sees another's prices.
What it does
- Scope catalogs, pricing and stores per customer
- Each customer sees only their own program
- One platform serves many clients privately
- Set it once; every surface respects it
The scope
Pick whose account you are working in
Scope is not a filter you apply to a list. It is the lens the whole platform is looking through, shown in the header at all times, and it decides where the work you do ends up. Switching takes a click and applies immediately.
Myself
The default. Anything you create is assigned to you — a store, a catalog, a discount — and the platform shows you your own work.
A customer
Scope to an account and you are working inside it. Everything you create lands on that customer, and the header tells you whose desk you are sitting at.
All customers
Browse every account at once — the view for a manager rather than an account handler. Anything you create still assigns to you, so browsing broadly never quietly misfiles work.
Unassigned
A deliberate scope: nothing lands here by default. It is where work with no account yet lives, rather than a bin things fall into by accident.
Search across the account list
By name, by company, or by role — because you remember the procurement lead at a club more often than you remember which contact record they are.
Pin the ones you live in
A scope you use every day sits at the top of the list. A rep with three big accounts shouldn’t be scrolling for them.
And the account behind the scope
Creating a customer is one drawer, opened from the same place you switch scope. It is deliberately short: the things an order actually needs, and nothing anybody has to invent.
Identity
A photo, first and last name, the company, and the person's role — so a contact is a person at an organization rather than an email address.
Contact
Email, phone and location.
Billing
A billing address with address suggestions, so a location is pinned precisely rather than typed into a free-text box. Plus a tax or VAT ID, shown on invoices.
Shipping
Same as billing by default, and separate the moment it isn't — which for a club with a clubhouse address and a home ground is most of the time.
Account
A tier — Starter, Growth or Enterprise — so how much an account is worth is on the record rather than in somebody's head.
Internal notes
Anything the team should know about this account. Internal, and never shown to the customer.
Each record also carries its own activity timeline, so who created an account and when is never a question.
Why a scope beats a filter
A filter changes what you see. A scope changes where your work goes — which is the thing that actually goes wrong on a shared account.
Nothing gets misfiled
A store built while scoped to a client belongs to that client. There is no step at the end where somebody remembers to assign it.
The account is legible
Catalogs, stores, discounts, cards and upcharges all carry a customer, so everything belonging to one client can be seen as one program.
Handover is possible
When a rep leaves, their accounts are records with owners, not a mailbox and a memory.
Scope decides which account you are working in. What each member of your team can reach is set separately in roles & access.
Every capability, one login
Customer scoping is one module of the Brikl platform. Start free and use them all, or see how they fit together.
Related: Catalogs · Roles & access