You decide what it does,
and for whom.
Role-based limits control which actions and tools each team can use through Mahadrone. An audit trail records every request and every action, so nothing happens out of sight.
Sahil
Export the payroll summary for September
Mahadrone
Payroll exports are limited to Finance. I can send an access request to the Finance admin.
Declined · logged to audit trail
Reports
Dashboards and exports
Access check: Finance only
Two layers of permission, both enforced.
First, your admins decide which actions each group can use through Mahadrone at all. Second, every action still runs within the requester's own permissions in the underlying tool.
Both have to allow it. If either says no, Mahadrone explains why and, where it makes sense, offers to request access from the right owner.
| Action | Everyone | Operations | Finance |
|---|---|---|---|
| Ask policy and process questions | Allowed | Allowed | Allowed |
| Book meeting rooms | Allowed | Allowed | Allowed |
| Submit own leave requests | Allowed | Allowed | Allowed |
| Pull team reports | Not allowed | Allowed | Allowed |
| Export finance summaries | Not allowed | Not allowed | Allowed |
Every request, route, action, and result.
The audit trail records who asked, what they asked for, which tool it was routed to, what action was taken, and how it ended: done, declined, routed to a person, or failed.
Filter it by person, team, tool, or outcome. Enterprise plans can export it for your own review process.
- Searchable by person, tool, and outcome
- Declined requests recorded with the reason
- Exportable on Enterprise
- Requested by
- Sahil Mane, Operations
- Channel
- Direct message
- Request
- Export the payroll summary for September
- Routed to
- Reports
- Role check
- Not allowed for Operations
- Result
- Declined, access request offered
The controls admins use most.
Groups from your directory
Build roles from the teams and groups you already manage.
Actions off by default
Every task starts switched off. You turn on what each group should use.
Inherited tool access
Actions use the requester's own rights in each connected tool.
Clear refusals
When something is not allowed, the employee is told why, in plain language.
Channel restrictions
Limit which channels the assistant can join and act in.
Audit exports
Export the audit trail for your own records on Enterprise plans.
The permission promise: it never acts beyond the access the person already has.
Mahadrone is not a way around your access controls. If an employee could not do something themselves in the connected tool, they cannot do it through Mahadrone either.
Who can change roles and permissions?+
Only users you make admins in the Mahadrone console. Changes to roles are themselves recorded in the audit trail.
Can we keep some tools connected but unavailable to certain teams?+
Yes. Connection and availability are separate. A tool can be connected and still limited to specific groups.
How long is the audit trail kept?+
Retention is set per workspace. See the Security page for how request and action logs are stored.
What does an employee see when a request is declined?+
A plain explanation of why, and where appropriate, an offer to request access from the owner.
Your first request is one message away.
Set up roles for our operations team
Sign upPrefer a walkthrough first? Talk to us