Users and access.

Who gets in, and how far.

Part 10 of 17 · 0 min 58 s

See all seventeen

Transcript

What the narration says, word for word (translated from the Spanish voice-over).

In this video: who gets into Batuta and what they can do inside.

Everyone with access has two things: a role, which defines what they can do, and a scope, which defines where they can do it. Scope matters once there's more than one venue. An administrator for the whole organisation sees everything; a venue supervisor can be given only their own, and won't see the others.

You invite by email, choosing role and scope at that moment. Whoever receives the invitation creates their password and lands straight on what's theirs. And there's read-only access, for someone who needs to look at the schedule without being able to move it: an owner, an accountant, a head of operations.

Want to see this with your own venue's shifts and staff? Write to us at usebatuta.com.

Recorded on a demo restaurant: invented names, no real person's data. There is no pilot running yet, so you will not see customer results here.

We're just getting started — and that works in your favor.

Our first customers work directly with the people building Batuta: we configure it with you, tune it to your operation, and your feedback shapes what comes next. We start with a hands-on pilot, and the price — simple, per location — is set together once it has proven its value.

Prefer email? hola@usebatuta.com