Site Factory
Site Factory is where stacked multi-site management happens. It has its own set of users, roles, and permissions to control access.
🔗 Site Factory Management Console Documentation
Key access concepts
- Users and Roles – Who can access Site Factory and their level of control
- Groups and Members – Organized teams within Site Factory
- Member types – Can be assigned one or more of the following roles:
- Member – Basic access
- Administrator – Full control over group sites
- Owner – The highest level of access for site management
- Sites and collections – Groupings of websites for easier management
User roles and responsibilities
Different roles have different levels of access across ASU’s Acquia-hosted platforms.
Stack roles
- Stack "Platform Admin" – Manages Site Factory stacks and contributes to the codebase, including Enterprise Technology and The College developers
- Stack "Site Builder" – Can create and manage sites, organize site collections and restore backups
- Stack Trusted Partner – Developer with limited access who can submit code changes but cannot merge them (requires special request, training and access to other systems. More details will be shared later.)
Site-level roles (for individual Drupal websites)
- Site Administrator – Has administrator rights within a Drupal site, including Enterprise Technology and The College developers
- Site Builder / Content Administrator – Manages content and configurations of site Content Editor – Can edit site content but has limited administrative controls
Need more information?
For the latest updates on permissions and access, refer to the official Acquia documentation:
Trusted partner responsibilities
What are trusted partners and who are they?
Access and responsibilities
- Site Factory users can request Trusted Partner access to maintain custom code for their sites
- Access is granted based on demonstrated need and technical capacity
- Trusted Partners can submit merge requests through the Enterprise Technology Web Platforms development pipeline in Acquia Code Studio
- Merge requests are reviewed by Enterprise Technology Web Platform developers, who may request security, accessibility, or branding improvements before merging the code into the platform for the next release
Ongoing code maintenance
- Each group with custom code in the Enterprise Technology Web Platform should have a trained and capable Trusted Partner responsible for updating their code
- This includes ensuring modules and themes remain compatible with the Drupal version targeted for upcoming releases
- Trusted Partners should have their code ready for testing at least one month before the target release
- Unmaintained or outdated custom code can block other sites in the stack from updating, which is a security and compliance risk
- If a site fails to update its code in a timely manner, Enterprise Technology Web Platform developers may:
- Disable outdated or non-compliant modules
- Implement temporary workarounds until the site owner resolves the issue
- In a multi-tenant hosting environment, platform integrity takes precedence over an individual site’s needs if development responsibilities are not met
Support for trusted partners
- Trusted Partner Collaboration Office Hours and a Trusted Partners Slack channel are available to provide guidance
- Enterprise Technology Web Platforms supports Trusted Partners by:
- Providing transparency into Enterprise Technology Web Platforms processes
- Helping Trusted Partners succeed through guidance and resources
- Communicating early and often to ensure upgrade compatibility
- Sharing best practices and upskilling developers
- Encouraging collaboration and ownership within the Trusted Partner community