Designing Separate Performer and Moderator Account Areas in Evolution CMS

Role-based account areas sound simple until the business process becomes real. In the original discussion, the site needed a personal account for moderators and performers, with different actions, different visibility rules, and a shared workflow around requests created by visitors.

The mistake here is trying to build a completely separate mini-site for every role. A cleaner Evolution CMS approach is to keep one account area and let role-based logic decide which blocks, actions, and resources each user can see.

Model the actors first

• Visitor: creates a request or submits an order.
• Moderator: reviews, distributes, or validates that request.
• Performer: processes only the items assigned to them.

Once the actors are clear, the content model becomes easier. The request itself can live as one resource or one structured record, while status, assignee, and workflow state can be stored in TVs or a dedicated table if the project grows beyond simple content editing.

Use one dashboard, not several disconnected systems

A good account area usually has:

• a shared entry page after login,
• role-specific dashboard blocks,
• filtered request lists for each role,
• status-change actions limited by permissions.

That gives moderators one view of incoming work and performers another view of only their assigned queue, without duplicating the whole interface.

What to keep editable

If moderators need to redistribute work, store the assignee and the current workflow stage in fields that can be changed safely. If performers should only update progress or upload results, expose only those fields or actions to them. Evolution CMS works best when the permission boundaries are explicit instead of being hidden inside giant conditional templates.

In practice, the most maintainable solution is a single account architecture with clear roles, filtered listings, and a predictable state machine. That is far easier to support than separate dashboards that duplicate templates, snippets, and routing rules for every user type.