Can each colleague view only the internal requests they created themselves?

Yes. In Jestor, the SMB template lets you configure permissions on internal requests so each colleague only sees the requests they created themselves, keeping requests private between different requesters.

How this permission setup works

Internal requests — such as access requests, hardware maintenance, or equipment swaps — can be configured to show only records linked to the logged-in user. This means that, at a certain stage of the flow, each person only sees the requests they opened themselves, with no access to requests made by other colleagues.

Profile	What they see
Regular colleague	Only the requests they created themselves

How to set up this view by requester

Go to the requests table's permission settings.
Set the rule to show only records created by the logged-in user.
Make the new-request form available to the whole team.
Use the requests dashboard for a consolidated view by category and stage, depending on each profile's access level.

Why choose Jestor

Privacy between requesters: each colleague tracks only what's theirs, with no mixing of other people's requests.
Organized categories and subcategories: each area sees only the options relevant to its type of request.
Public request form: any colleague can open a new request directly through a link.

Can a manager see all requests, even ones from other colleagues?

Permissions can be set up differently by profile, allowing managers to have a broader view while colleagues see only their own.

Are request categories fixed or customizable?

They're fully customizable: new categories and subcategories can be created and linked as the company needs.

Can a colleague chat about their request from within the record itself?

Yes, each request has its own chat, where the colleague can talk with the team responsible for handling that request.

Reference video

Check out more hands-on tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI.

Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

Why does a removed user show as inactive instead of being deleted, and what does that preserve in the history?

In Jestor, removing a user doesn't delete them from the system: their status changes to inactive, specifically to preserve the history of everything that person changed on records in the past. Why this logic exists If a user were completely deleted, the entire history of actions they performed

Can a text inside a card be shared with only the selected people?

Yes. In Jestor, each document connected to a card can be shared with only the specific people added to it, giving individual access instead of automatically opening it up to the whole team. How selective sharing works When creating a document inside a record, you need to manually add the

How do you lock a document as read-only to prevent accidental edits inside a card?

In Jestor, any document connected to a card can be locked for editing, making it read-only, which prevents someone from accidentally changing the content when reading that text. How locking a document works Inside the documents tool (Docs) connected to records and cards, you can lock a specific text

Where can you activate the builder directly from the Home to quickly access editing mode?

In Jestor, you can add the builder block directly to the home page, letting you access construction mode quickly with no need to first navigate to another app. How to add the builder to the Home When personalizing the Home, one of the available blocks is the builder option, which