Permissions decide what each teammate can see and do inside your Tambala business.

Choosing them carefully is important because different people need different levels of access.

The simplest rule is:

Give someone enough access to do their job well, but no more than they need.

Start with the person's job

Do not begin by looking at the permission list and asking which boxes you could tick.

Start by asking:

What is this person responsible for?

If their job is to prepare and complete customer orders, give them the order access they need.
If they manage your products, they may need product access.
If they run your accommodation business, they may need booking access.
If they only scan tickets on event day, they usually need check-in access rather than full event management.

Permissions should follow responsibility.

Viewing and managing are different

Tambala may separate permissions that allow someone to see information from permissions that allow them to change it. That difference matters.

For example, someone may need to see an order to help with fulfilment without needing permission to cancel it or change its status.

Someone may need to see sales performance without needing access to request payouts.

Whenever Tambala gives you a choice between viewing and managing, ask whether the teammate genuinely needs to make changes.

If they only need information, viewing access may be enough.

Orders

Order permissions are useful for people responsible for fulfilment and customer purchases.

A person who only needs to check incoming orders may only require viewing access.

A person who prepares packages, marks orders ready, updates fulfilment or manages order status will usually need stronger order-management access.

Do not automatically give payment or business-settings access to someone simply because they process orders.

Products

Product permissions are useful for teammates responsible for keeping your catalogue accurate.

Someone may only need to see your product information.

A person responsible for creating listings, changing prices, updating stock or managing product information will need management access.

Because product changes affect what customers can buy, give this access to people who understand your catalogue and pricing.

Events

There are two very different types of event access.

An event manager may need to create events, change event details, manage ticket types and deal with wider event operations.

A check-in teammate may only need to scan tickets at one particular event.

Do not give every gate worker full event-management access.

For people working only at the entrance, use the limited check-in access available and assign them only to the events they are actually working.

See Manage Event Check-In Staff for the full process.

Stays and bookings

A teammate who helps run accommodation may need access to bookings.

This can include viewing reservations, preparing for guests, managing booking information and helping with the stay process.

Because bookings contain customer information and can affect availability, only give this access to people involved in that part of the business.

Analytics

Analytics access lets someone understand how the business is performing.

This can be useful for a manager, marketing teammate or someone responsible for growth.

However, seeing performance data does not necessarily mean the person should also have access to payments.

Treat business performance and control of money as separate responsibilities.

Earnings and payments

Financial access should be given carefully.

Someone may need to see earnings without being allowed to change payout details or request money.

Permissions that allow a person to manage payouts, bank information, mobile money information or other financial settings should normally be limited to the owner or a small number of highly trusted people.

Before giving financial access, ask whether the person's job truly requires it.

If not, keep it with the owner.

Customers

Customer permissions may allow a teammate to see customer information or communicate with buyers.

This is useful for people handling customer service, problems, reviews or support.

Customer information should be treated responsibly.

Do not give access simply because someone occasionally helps the business. Give it to people whose work actually involves customers.

Business settings

Settings can affect how your whole business operates.

This may include store information, fulfilment options and other important account details.

Because these changes can affect every customer and teammate, settings access should be limited to people who are genuinely responsible for running the business.

Use presets as a starting point

Tambala may offer ready-made permission groups for common jobs.

For example, there may be options designed for:

Order staff — people who mainly handle orders.

Event managers — people responsible for running events.

Check-in crew — people who only scan attendees at assigned events.

General staff or managers — trusted people who handle several areas of the business.

Presets can save time, but do not treat them as permanent rules.

After choosing one, look at the permissions and remove anything the teammate does not need.

A few practical examples

If Thandi helps pack and process orders, she needs the tools required to manage those orders. She probably does not need access to your payouts, events or business settings.

If Peter manages your online catalogue, he may need product-management access and perhaps analytics if he is responsible for improving sales. He may not need customer or payment access.

If Grace runs one event at the gate, she may only need ticket check-in access for that event.

If Martha manages your accommodation business, she may need booking access and perhaps customer communication, depending on her responsibilities.

Permissions should reflect these real jobs rather than titles alone.

When someone's job changes

Review their permissions.

Do not simply add new permissions on top of everything they already had.

Ask whether some of the old access should now be removed.

Someone moving from event operations to product management may no longer need access to event check-in.

Good access management changes with the person's role.

The important thing to remember

More access is not a reward or a sign of trust.

It is a tool someone needs to perform a particular job.

Give the right person the right access for the work they are doing.

Nothing more.

That keeps the business easier to manage and reduces unnecessary risk.