Managing Users and Permissions

The safest way to read permissions in wallmarkets today is to stay close to what the product actually exposes.

The current app is much simpler than a full enterprise admin console with custom roles, invitation workflows, and a deep permission matrix in every account. If you write internal process assuming all of that already exists in the UI, you will confuse people.

This guide explains the practical access boundaries that matter right now.

What is clearly controlled today

Three permission boundaries matter most in the current product:

• the signed-in account
• the selected business context
• the API keys created under that account

Those are the lines readers should understand first.

Business scoping matters

Deliveries, returns, products, and supermarkets are tied to the current business context.

That means access is not just about being logged in. It is also about which business the account is operating inside at the time. When people say they "cannot find" a delivery or product, the problem is often context before it is anything more exotic.

Account ownership still matters

Even without a heavy role-management UI, some actions are naturally owner-level responsibilities:

• keeping account details accurate
• handling billing or plan questions
• managing API keys carefully
• deciding when destructive actions such as account deletion are appropriate

If your team shares those responsibilities informally, it is worth making them explicit.

API keys are a permission surface too

One of the easiest permission mistakes teams make is thinking only about interactive users and forgetting API credentials.

In practice, API keys are access holders. If a key is active, named badly, and no one remembers which system uses it, that is a permissions problem even if the login UI looks tidy.

A good operational rule is simple:

• one key per integration
• clear naming
• revoke old keys aggressively

What the public account UI does not currently give you

Readers often look for:

• a full roles table
• invite and revoke flows for teammates
• custom role design
• granular per-feature permissions

Do not assume those controls are present for every account just because they are common in other SaaS tools. The current wallmarkets experience is more restrained than that.

How teams should work safely anyway

Even with a simpler access model, you can keep the account sane.

Avoid shared credentials

If multiple people need access, shared passwords create confusion fast and make security incidents harder to unwind.

Decide who owns which workflow

At minimum, be clear about:

• who creates deliveries
• who reviews returns
• who exports reports
• who owns API keys
• who speaks for billing

Review access during team changes

Ownership confusion usually shows up when someone leaves, changes role, or hands an integration to someone else.

When you need tighter control

If your team needs formalized roles, audit-style user management, or stricter enterprise controls, treat that as a product and account-planning conversation rather than trying to fake it with shared credentials and tribal knowledge.

The honest answer is better than pretending the permission model is more mature than it is.

Related guides

• Security settings
• Updating your profile
• Billing and subscription