Architecture
Core Architecture
Platform Governance and Operations
8 min
activate enforces governance through a combination of role based access control, controlled design access, configurable permissions, and detailed audit history these capabilities ensure that low code configuration can be safely delegated while maintaining appropriate oversight and accountability role based access control activate applies role based access control at both the system level and the object level users are granted only the permissions required for their responsibilities, with elevated access explicitly assigned rather than implicitly assumed platform administrators platform administrators have global rights to view and modify all areas of the activate platform this includes system configuration, security settings, workflow and service design, and operational controls access to these capabilities is restricted to administrative roles, ensuring that platform governance remains under it control approvers approvers have access only to the jobs and requests they are assigned to approve, and only while those requests are awaiting approval approvers can review relevant request context, take approval actions, and track outcomes they do not have access to workflow design, service configuration, or platform administration object owners activate supports object level ownership, where users are granted additional rights only for the specific objects they own for example, owners of distribution lists can add or remove members directly without requiring approval requests for membership changes are routed to the relevant owner, who acts as the approver for those requests this model enables delegated administration while preserving clear boundaries and accountability configurable roles and permissions activate includes a comprehensive security and permissions framework that allows organisations to create custom roles and assign permissions to specific tasks or object types permissions can be scoped to defined responsibilities, allowing organisations to align platform access with internal policies and operating models rather than relying on a fixed role structure default access model by default, users have read only access to designed objects within activate additional role memberships are required to create or modify objects such as service catalogue items, workflows, or administrative configuration this default posture reduces risk and ensures that elevated access is granted intentionally read only access applies to designed objects only users can still participate in workflows as approvers or request targets without design or administrative permissions workflow design governance the ability to create or modify workflows is restricted to elevated roles only users without these roles cannot alter workflow logic or configuration, but they can still participate in workflows as approvers or as the target of a request this separation ensures collaboration without exposing design or governance controls activate studio access controls activate studio provides web based administrative capabilities for system configuration and the design of tasks, services, and workflows access to activate studio is locked down out of the box and restricted to system administrators this ensures that administrative and design functions are clearly separated from operational usage audit logging and change history activate provides robust audit logging for both jobs and users the platform records the history of actions performed against an object, such as a job, as well as actions performed by an object, such as a user this supports traceability and operational oversight all configuration parameters within activate maintain unlimited change history, including who made a change, when the change occurred, and what was modified changes are captured using a diff mechanism to provide precise visibility into configuration evolution over time governance summary activate’s enforced role separation, controlled access to design capabilities, configurable permissions, and comprehensive audit history provide strong support for enterprise governance and operational control these capabilities enable low code configuration and business participation while maintaining it oversight, consistency, and accountability