Articles

Who Edits Your Company Website? The Dashboard and Team Permissions

A guide for company owners in Saudi Arabia: what your team edits itself, how to assign roles and permissions, and how to separate the draft from publishing

A company website should not depend on one person or on the developer for every change. A clear Dashboard lets your team edit pages, articles and forms itself; roles and permissions give each person only what their work needs; and separating the draft from publishing protects the site from mistakes.

The GenAI Web Studio Dashboard: the Website, Blog, Forms and Team menus, and the page settings

The problem: a website only one person can edit

Many companies launch their website, and then it stops on launch day. The reason is usually that every change passes through one person: the developer, an employee who knows the password, or an outside company waiting for a formal request.

The result is familiar:

  • An offer that ended is still on the home page.
  • An old phone number on the contact page.
  • A new service that the site's visitors never hear about.
  • One password shared by several employees.

The answer is a website with a Dashboard your team works from, where each person has their own account and role.

What does your team edit itself?

After launch, these are everyday tasks your team should do without waiting for anyone:

  • Editing page texts and images, and adding a page for a new service.
  • Ordering the site's main menu.
  • Writing and publishing articles and news.
  • Creating a form for a new request and reading its answers.
  • Editing a page's title and description in search results.

What needs a specialist is what touches the site's build itself: connecting the domain, technical settings and tracking tools. That is handled by whoever set up the site for you.

Roles and permissions: each person gets only what they need

Information security has a known principle called "least privilege": each user gets the least access they need to do their work. The US National Institute of Standards and Technology (NIST) defines it in this sense.

On a website, that means roles such as:

  • Content writer: writes articles but does not change the site's pages.
  • Sales team: reads form answers but does not edit content.
  • Marketing manager: edits pages and publishes articles.
  • Account owner: adds team members and sets their roles.

When an employee leaves, review the team list and switch off their account, instead of changing a password everyone shares.

Draft and publish

Separating the draft from publishing protects your site from mistakes:

  1. The employee edits the page or article in a draft.
  2. The published site stays as it is during editing, so visitors never see unfinished work.
  3. Someone with the publish permission publishes the change after reviewing it.

This way a new writer can work on an article without worrying that it appears to people before it is finished.

Questions to ask before you choose

When choosing who builds your site, ask about the Dashboard itself, not only about how the site looks:

  • Can my team edit pages and articles without coming back to you?
  • Does each employee have their own account, or do we share one?
  • Can I decide what each role sees and does?
  • Does a change show to visitors at once, or after publishing?
  • What language is the Dashboard interface in, and in which languages do I write content?

And if you are starting from scratch, also read the steps of designing a website for your company.

The Dashboard in GenAI Web Studio

With GenAI Web Studio your team runs the website from one Dashboard:

  • Website: pages in Arabic and English from a section library, with adding, ordering and hiding sections, the menu, the media library, and publishing per page and per language. The published site stays as it is until you publish.
  • Blog: articles and categories in Arabic and English.
  • Forms: building forms and reading their answers.
  • Team: adding a member with a set role, and creating roles where you choose each one's areas: Website, Blog or Forms. A role without a permission neither sees nor does the thing, and a published article can be changed only by someone with the publish permission.

What you should know: the Dashboard interface is in English, while you write the content in Arabic and English. Duplicating a page to the other language copies it; it does not translate it. Our team sets up the site and the first roles for you, and stays with you step by step.

Conclusion

A website your team edits itself, with clear accounts and roles and publishing after review, stays alive after launch day. If you would like us to set up a website with a Dashboard and a team with permissions for you, contact us from the <a href="/en/page/contact">contact page</a>.

Frequently asked questions

Does my team need to know programming to edit the website?

No. Everyday editing is done from the Dashboard with simple fields: texts, images, sections and the menu. What touches the site's build is handled by whoever set it up.

Why not share one account?

Because you cannot tell who changed what, and an employee leaving means changing the password for everyone. One account per person with a set role is clearer and safer.

What is the difference between saving a change and publishing it?

Saving keeps the change in a draft visitors do not see; publishing makes it appear on the site.

Can I give an employee access to the blog only?

Yes, with a role that has the Blog area only, so they write articles without changing the site's pages.

References

  1. least privilege - Glossary · NIST Computer Security Resource Center (CSRC)

Related articles