Plugin Access Governance Hub: Centralised Audience Reporting and Bulk Management
Problem
As Moveworks deployments mature, organisations often have:
- Legacy Creator Studio plugins (Events, Paths & Queries)
- Agent Studio (Classic) plugins
- Tool Studio plugins
Access management becomes increasingly difficult because audience rules are distributed across individual configurations.
Administrators cannot easily answer:
- Who has access to what?
- Which plugins target a specific department?
- Which plugins are available to a given user?
- Which plugins are no longer aligned to current organisational structures?
- What changed over time?
Proposed Solution
Create a Plugin Access Governance Hub that provides:
Centralised Reporting
- Single view of all plugins and agents
- Audience definitions
- Launch criteria
- Status (enabled/disabled)
- Creator/owner
- Last modified date
User Access Lookup
Search by:
- User
- Group
- Department
- Role
- Location
Return:
- All plugins available to that audience
- Effective access based on launch conditions
Impact Analysis
Before making a change:
- Show how many users will gain access
- Show how many users will lose access
- Highlight affected departments and groups
Bulk Administration
Update audience rules across multiple plugins:
- Replace department
- Replace location
- Replace group
- Replace role
- Enable/disable multiple plugins
Example:
"Department Technology Services renamed to Digital & Technology. Update all plugin launch criteria that reference the old department."
Governance Dashboard
- Orphaned plugins with no owner
- Plugins with overlapping audiences
- Unused plugins
- Recently changed permissions
- Access review recommendations
Export Capability
Export to CSV/Excel:
- Plugin name
- Type
- Owner
- Audience rules
- Estimated audience size
- Status
Business Value
- Improves governance and auditability
- Reduces administration effort
- Supports security and least-privilege access principles
- Simplifies organisational restructures
- Enables easier migration from Creator Studio and Agent Studio (Classic) to Tool Studio
- Gives administrators visibility across the entire automation estate
As customers adopt Tool Studio while continuing to operate legacy Creator Studio events, queries & paths, Agent Studio (Classic) plugins, audience management becomes fragmented. A centralised access governance experience with reporting, search, impact analysis and bulk updates would significantly improve administration, compliance and platform scalability.
Here’s what it could look like
