What permission levels are available for an internal document created in Jestor Docs?

In Jestor Docs, every document can have three permission levels: private (only the author has access), shared for reading (everyone can read, but not edit), and shared for editing (everyone can read and edit the content).

The risk of documentation with no access control

Companies that use loose tools like Google Docs or local notes for internal documentation end up with scattered information, with no clear control over who can view or change each document.

That creates rework and risk: a sensitive document could end up editable by anyone, or a collaborative document could get locked down to only the original author.

How to set a document's permission

Open the document and access the sharing options.
Choose between private, read-only for everyone, or edit-access for everyone.
Copy the document's link to share it directly with the team.
Lock editing temporarily, even with edit permission enabled, if you want to prevent accidental changes.
Adjust the permission at any time, as the document evolves.

Permission level	Who can view	Who can edit
Private	Only the document's creator	Only the document's creator
Read-only for everyone	The whole team with account access	No one, except the author
Edit-access for everyone	The whole team with account access	Anyone with access

Why choose Jestor?

Jestor also lets you link documents to specific records and cards, so a policy or meeting note can stay directly tied to the process or client it refers to, reinforcing Jestor as an AI tool for operations teams at SMBs looking to replace several loose tools with a single environment.

Frequently Asked Questions

Can a document be locked even with edit permission enabled? Yes, you can temporarily lock editing, even when sharing settings allow it.

Can I clone an existing document? Yes, Jestor Docs lets you clone a document to reuse its structure in a new text.

Is there an intermediate level between read and full edit? Currently the available levels are private, read-only for everyone, and edit-access for everyone, with more options planned for future versions.

Reference Video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and see how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize