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

Yes. In the request module of Jestor's SMB management template, permissions are configured so each request is visible only to the logged-in user who created it, without one employee seeing what another registered.

Why restrict internal request visibility by employee?

Internal requests — like a reimbursement request, software access, or an equipment swap — often contain information that only concerns whoever opened that ticket. Letting everyone see all of their colleagues' requests creates unnecessary noise and can expose information that doesn't need to be shared.

How does this permissioning work in Jestor?

An employee creates a new request, choosing a category and subcategory — for example, finance, with invoice and reimbursement.
The request stays registered and visible only to whoever created it.
The person assigned to handle that category can track and respond through the request's internal chat.
On the requests dashboard, you can track how many requests exist by category and by stage, without exposing each one's individual content to the whole team.

Who accesses it	What they can see
Employee who created it	Only their own requests
Consolidated dashboard	Count by category and stage, without exposing individual content

Why choose Jestor?

This kind of logged-in-user permissioning is essential for SMBs growing fast: Jestor's automation organizes that access control without requiring complex permission setup from a dedicated IT team.

Frequently Asked Questions

Can the category owner see all requests of that type? Yes, whoever handles the category tracks related requests through the chat and the process stage.

Can this be configured by category and subcategory? Yes, each category can have linked subcategories, like invoice and reimbursement within finance.

Can a public form be used for these requests? Yes, it's possible to make a public form available so anyone on the team can open a new request.

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 discover 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