Users Guide
Users Guide
Users and permissions determine how teams collaborate safely inside PageFace and FaceFlow.
As the website team grows, access should reflect real responsibilities. The goal is not to give everyone the same control. The goal is to let each person do the work they need to do without creating unnecessary risk.
When To Review Users and Permissions
Review users and permissions when:
- a new team joins the website workflow
- different business units own different sections
- editors need access but not full control
- administration and day-to-day editing should be separated
- review or publishing authority should be limited
If team structure changes, access design should usually change too.
Recommended Workflow
- Define responsibilities
- Create a small number of clear roles
- Assign users to the right roles
- Limit access by section when needed
- Review permissions whenever ownership changes
What Makes a Safer Team Workflow
Strong access design usually:
- separates editors from administrators
- limits higher-risk actions to the right people
- keeps roles understandable
- reflects actual ownership of site sections
- gets reviewed regularly
The best permission model is usually the one that people can understand and maintain.
Common Use Cases
- content teams managing pages only
- marketing teams managing campaigns and forms
- support or moderation teams reviewing submissions
- regional teams managing their own site sections
Common Mistakes
- giving full access too broadly
- creating many overlapping roles with unclear differences
- forgetting to remove or update access after personnel changes
- treating all editors as if they own the whole site
- making roles so complex that nobody understands the differences
Team Guidance
- align permissions with actual responsibilities
- keep administrator access limited
- use section ownership where different teams manage different branches
- review inactive or outdated accounts regularly