When several people help run a business, it can sometimes be difficult to remember who changed what.

Tambala's teammate activity and audit information gives you a record of important actions connected to your team.

Use it when you need to understand what happened, check an unexpected change or review how access is being used.

What the activity record is for

Imagine a customer says their order was cancelled, but nobody remembers cancelling it.

Or a product price changes unexpectedly.

Or an event setting is updated shortly before tickets go on sale.

Instead of asking everyone and relying only on memory, you can check the activity record.

The goal is accountability, not watching every small thing your teammates do.

Open teammate activity

From the seller dashboard, open Teammates and look for the activity or audit information available there.

Tambala may show actions connected to teammate management as well as actions teammates perform while working in the business.

The exact information shown depends on the action, but it may include who performed it and when it happened.

Management activity

The audit record can help you understand changes made to teammate accounts.

For example, it may show when someone was:

Added to the business.

Given new permissions.

Disabled or enabled.

Assigned to an event.

Removed from the team.

Had their access changed.

This is useful when you want to know who had access to something at a particular time.

Teammate activity

Tambala may also record important actions performed by teammates while using the seller dashboard.

This can help you trace changes to areas such as orders, products, events or settings where activity logging is supported.

You do not need to understand technical request names or system details to use the record effectively.

The useful questions are simpler:

Who performed the action?

What changed?

When did it happen?

Then compare that with what was supposed to happen.

Use the log when something goes wrong

Start with the event you are trying to understand.

For example, if an order was unexpectedly changed, identify approximately when it happened and which teammates had order access.

Then check the relevant activity around that time.

If the record shows a particular teammate made the change, speak to them and understand why.

It may have been a mistake, a misunderstanding or the correct action that was simply not communicated.

Do not assume malicious behaviour just because someone's name appears in the activity record.

Use the information to establish what happened first.

Use activity to improve processes

The audit log is also useful when nobody has done anything wrong.

Suppose several teammates keep changing the same order back and forth.

The problem may be unclear responsibilities rather than the people themselves.

If one employee repeatedly has to correct another person's stock changes, the team may need better training or clearer ownership.

Activity records can reveal where your operating process needs improvement.

Review access after an incident

If an activity review shows that someone could make a change they should not have been responsible for, look at their permissions.

The solution may be to remove unnecessary access rather than simply telling them not to use it again.

Permissions are there to turn responsibilities into actual system boundaries.

See Choose the Right Permissions for Teammates if you need to adjust someone's access.

Check event activity when necessary

Activity records can be especially useful around event check-in.

When several teammates work at different gates, knowing who handled a ticket can help if an attendee later disputes what happened.

Do not ask gate staff to share one account.

Individual teammate access makes event records much more useful.

For event-specific setup, see Manage Event Check-In Staff.

Do not use the activity log to micromanage

The purpose of an audit record is not to inspect every click an employee makes.

If your team has clear responsibilities and the business is running normally, they should have room to do their jobs.

Use activity information when it helps answer a real question, investigate something unusual, improve a process or review access.

Trust and accountability can exist together.

Keep important business decisions clear

The audit log can show that someone performed an action.

It cannot always explain why they did it.

For important decisions, your team should still communicate.

If a manager cancels a major order, changes an event date or makes another important decision, there should be a clear business reason that the relevant people understand.

Good records support good communication. They do not replace it.

When to contact Tambala

If the activity record shows something you cannot explain, or you believe someone accessed the business without permission, secure the account first.

Reset passwords or disable affected teammates where necessary.

Then contact Tambala support if you need help understanding activity or protecting the account.

Keep any useful dates, teammate names and relevant order, event or transaction references available.

The important thing to remember

The activity record helps answer:

Who did it?

What happened?

When did it happen?

Use those answers to solve problems, improve your processes and keep access appropriate.

The goal is not to watch your team constantly.

It is to make sure that when something important happens, your business has a record you can rely on.