Gated System Admin Access

One of the most common use-cases for our API are interfaces which provide a 'gated' access to only a sub-set of system admin functionalities. It is not always desirable to expose the full range of system admin actions to all of your staff. For example; they could severely alter the configuration of the instance in a non-trivial way. However, you might still want a certain team to be able to carry out lower-level administrative tasks, (re-sending site invite emails, checking on the status and size of sites, reporting on when users were added to the system, etc, etc..)

This example is a basic Help Desk ticketing system for a support team divided into 1st and 2nd line workers. 1st line workers can search for users, remove and re-invite them to sites, search sites and report on their properties, as well as add in new organisations to their instance. For tasks which cannot be carried out by the 1st line team, they can create a helpdesk "ticket" for the 2nd line team, (who we assume actually have a user account in Collaborate), to pick up. Those users can even 'push' the tickets into their collaborate instance's tasks modules.

Search for users by email address, re-invite or remove:

Search for sites by sitename, inspect and message site-owner:

Search for organisation by either name or registered email domain:

...and add a new org: 

Some of the native helpdesk functionality from 1st line group perspective (user profile, activity feed): 

2nd line users can edit tasks submitted by the 1st line team: 

Leverage Collaborate's more sophisticated Task management functionality by 'pushing' a task to Collaborate: 

Evidence of the pushed task in Collaborate!