imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Give editors the access their work requires.

Begin with tasks and responsibilities rather than making everyone an administrator. Document who can edit, publish and manage accounts. Test permitted and prohibited actions in an isolated environment with fictional data.

From responsibility to verified access

  1. Describe

    List actions the role needs.

  2. Limit

    Grant justified rights only.

  3. Test

    Try permitted and prohibited tasks.

Distinguish different responsibilities

A writer may need to update a draft without making it public. A publisher may approve content without managing users or system settings. One person can hold several roles, but that should be a deliberate choice.

Permission is different from instruction. A document saying a writer must not publish does not prevent a button that allows publication. Establish which constraints the installation can enforce and which parts rely on organisational procedure.

Write a small task matrix

List real actions and identify who needs them. Start with drafts, media, publishing and account management. Add page or language restrictions only when they are needed and the system actually supports them.

Least privilege helps limit unnecessary rights. It does not replace server-side checks. Hiding a control in the interface is not, by itself, sufficient access protection. Ask the people responsible for the system how the agreed restrictions are enforced.

ActionDecision
Edit draftsWho needs to change this content?
PublishWho may make it public?
MediaWho may upload or replace resources?
Manage accountsWho may change someone else’s access?

Try two separate test accounts

Create bounded exercises for a writer and publisher in a safe test environment. The writer should complete the intended edit but be unable to perform a prohibited administrative action. The publisher should complete the approved task without needing broader temporary access.

Record expected and actual outcomes. A successful prohibited action is a real permission defect. Do not test against other people’s actual content. Security review and checks at the server need the people responsible for the system.

Plan for role changes

Review access when people join, change responsibilities or leave. Assign someone to approve accounts and confirm unnecessary rights are removed. Avoid shared accounts that obscure responsibility and follow-up. Connect the matrix to publishing and handover so it is actually used. This guide is planning support, not a security certification of your installation or a claim that every product provides all the restrictions discussed. Record unsupported requirements explicitly rather than treating a desired role as an implemented safeguard.

Sources and further reading

Questions, answered

Are hidden buttons sufficient protection?

No. The system owner needs checks where the action is executed, not only in its interface presentation.

Must every task have a different person?

No. Small teams may combine roles, but the person’s actual rights should remain clear.

IMBAHUB

Let’s plan your website

Begin with tasks and responsibilities rather than making everyone an administrator. Document who can edit, publish and manage accounts. Test permitted and prohibited actions in an isolated environment with fictional data.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.