Tenant administration

[RichardDCG]

Is it possible to have different admin levels per tenant?  Set users as full admin or just able to modify accounts, but to do this per tenant not global.  There may be tenants that want to self manage the PBX completely and others that want to be able to manage extension names etc..

[Vodia PBX]

Its in "thought" stage. We have a few hardcoded flags like for handling trunks, but eventually we need something similar like the groups in the tenants. 

[RichardDCG]

On 10/25/2021 at 11:55 PM, Vodia PBX said:

Its in "thought" stage. We have a few hardcoded flags like for handling trunks, but eventually we need something similar like the groups in the tenants. 

Is this likely to progress?  It could be handy to allow tenants to 'self manage' to differing degrees.  i.e. one tenant allow to manage their own extensions - naming etc.  And another to be able to manage their whole PBX, change trunk destinations, add ring groups, queues etc.

At the moment it is all or nothing global.

[Vodia PBX]

We did make some progress, e.g. there are roles for managing the shared address book, queues and access recordings. IMHO things like changing trunk destinations should be done by a domain administrator and there should be no such role for end users. But for example more management of ring groups could be something than an end user could do. 

[RichardDCG]

There are global tenant admin privileges - change Trunks, Dial plans, Accounts, ANI.  But this is for every tenant.  Ideally what I would like is per tenant to have permissions granted for varying degrees.  Updating extension names, ring groups, uploading hold music etc.  Potentially there would also be need for a tenant admin with complete control of their own tenancy.

[RichardDCG]

Is this something that can be incorporated into a build?  It would be handy to be able to offload some tasks - extension names, ring group membership, hold music etc to a tenant to semi self manage without allowing them complete access.  Other tenants may be able to handle the admin of the PBX themselves and could be granted more privilege, at the moment this is all a global setting.

[RichardDCG]

we have some tenants that would like to self manage (to a degree) their own PBX instance.  Is there a way we can set what they can and cannot do per tenant and not a single global setting?

Option to rename extensions, add/remove from queues and ring groups.  Add permissions to extensions etc.  Without being able to add extensions or trunks.

[Vodia support]

Hi, Richard 

We only have tenant admin permission, for users to log into thier own tenant but cannot change certians settings, of course this is in a multi-tenant env.  

•  Queues and ring groups permission already available  
• Add pernission this can already be done with policy groups 
• Being able to add extensions or trunks

 

 

 

[RichardDCG]

Thanks, yes I understand the permissions.  However, how can a user add a new extension to a queue or the queue flow (I can see how they can be added/removed if already set in the admin)?

How does a user change the ring group?

How can a user manage the names of other extensions?

 

There are some menial tasks that can be managed by a local user without having to create an admin task.  I envisage this as a user admin login with specific tenant privileges and not via ext.?  Is this a viable option?

[Vodia PBX]

Totally agree. We want managers do that job without giving them tenant admin permissions. The "manage queue" permission does that — all we need now is to put that into the front end. A new version is in the making we somehow need to put that on the do-to-list.