Only in SEQUESTO · Fine-grained access management
Everyone sees just what they need. You decide, down to the detail.
Give each person and each team exactly the access they need: to a project, a folder inside it, a single document or even a single question, a Knowledge Hub document or a dashboard. View or edit, nothing more. James, SEQUESTO's AI bid agent, follows the same rules.
Access is a property of every question, document and folder, not a setting on the project, so people, teams and James all work inside the same boundaries.
SENSITIVITY
Why is access on bids so hard to get right?
A bid holds the most sensitive mix of documents a company has. The price sheet only finance and the bid director should see. CVs with personal data. A client reference under NDA. And next to them, a technical annex every expert needs to open.
01
Two choices only
Most tools give you two choices: someone is on the project, or not.
02
Margins seen or annexes requested
So either the sales lead sees the margins, or the expert can't open the annex and asks for it by e-mail.
03
An AI that reads everything
And once an AI is added, it often reads everything in the project, whoever is asking.
04
A decision at every level
SEQUESTO lets you decide at every level, for every person and every team.
Before / With SEQUESTO
Before
- On the project or not
- The price sheet in a separate tool, "for safety"
- Access given person by person, forgotten when people move
- The AI reads everything in the project
- "Who gave her access?"
With SEQUESTO
- Access per project, folder, document and question
- The price sheet in the bid, visible to finance and the bid director only
- Give access to a team; people joining or leaving the team are covered
- James reads only what the person asking may read
- Every access change on record
LEVELS
Decide at every level
At each level, access is view or edit, given to a person, a team or everyone in the company. Folders pass their access down to what's inside them, so you set it once and change it only where a document or question needs something different.
01
Projects
Decide who can open the bid at all.
02
Folders, documents and questions
Inside a project, use a "Pricing" folder for finance only, a "CVs" folder for HR and the bid lead, and a single question on subcontracting for Legal only.
03
Knowledge Hub
Decide which teams can use which past bids, policies, CVs and certificates.
04
Dashboards
Keep them private, or share them with a team, a few people or the whole company.
TEAMS
Teams, not lists of names
Set up your teams once: Bid office, Finance, Legal, HR, Security, each business unit.
01
Access given to a team
Give access to a team, and it holds for everyone in it.
02
Joiners and leavers covered
When someone joins Finance, they see the price sheets the day they join. When someone leaves, their access goes with them.
03
No lists of names
No list of names to keep up to date on every bid.
AI PERMISSIONS
James sees only what the person asking may see
When James drafts an answer for a sales lead, he can't use the price sheet that sales lead isn't allowed to open, and he can't search Knowledge Hub documents outside their access.
01
Same permissions as the asker
The AI works inside the same permissions as the person who asked.
02
Nothing leaks by phrasing
Nothing leaks through a well-phrased question.
RECORD
Every access change on record
Access granted, access removed, a folder made private, an owner changed: every change shows who made it and when. Admins search the record by person and date. See who did what.
An example: one bid, five levels of access
A staffing company answers a tender from a Swedish regional healthcare authority for temporary nurses in three hospitals.
Bid office edits the project
The bid office team can edit the whole project.
Account managers edit one folder
Account managers can edit the "Service delivery" folder and view the rest, except pricing.
Finance owns pricing
Finance can edit the "Pricing" folder. Nobody else can open it.
HR owns the CVs
HR can edit the "CVs" folder, with its personal data.
Sales sees the result
Sales can view the final response and the dashboard of open tenders, nothing else.
James stays inside the access
An account manager asks James to draft the service delivery section. James uses that folder and the Knowledge Hub documents the account manager may read, and never the pricing.
SET-UP
How it works
Set up your teams once.
01
Share at any level
Share a project, folder, document, question, Knowledge Hub document or dashboard with people, teams or the whole company, as view or edit.
02
Folders pass access down
Change access only where a file needs something different.
03
James follows the same rules
He follows the same rules, and every change is on record.
Related features
Security & governance
Your bids hold prices, CVs and client names, and a dozen people work on them, with an AI alongside. SEQUESTO lets you decide who sees what, control what James may do, see who did what, and know how every bid is going.
Learn more →See who did what
Every file created, moved, shared or deleted, every comment and every access change is on record, with the person who did it and when. You also see who works on which bid and how much time it takes, so you manage the team on facts.
Learn more →Knowledge Hub
James, SEQUESTO's AI bid agent, drafts from your past bids, policies, CVs and certificates. No Q&A library to build first, and every answer shows where it came from.
Learn more →Your reports, in your format
The board pack, the monthly pipeline e-mail, the win rate per business unit: build them inside SEQUESTO. From then on there is nothing to maintain. Every number stays current, one click from the bids behind it.
Learn more →Data sovereignty
When your SEQUESTO account is created, you decide where your data is stored: in the EU or in the US. Your tenders, answers and knowledge stay there, and the AI that works on them runs in the same region.
Learn more →Frequently asked questions
Yes. In SEQUESTO, admins decide who can see and edit each project, folder, document, question, Knowledge Hub document and dashboard, per person or per team, and James follows the same rules.
Yes. Give access to a team and it applies to everyone in it, including people who join later. People who leave the team lose that access.
View and edit, given to a person, a team or everyone in the company. Folders pass their access down to what is inside them, and you can change it for a single document or question.
Yes. When James works for someone, he only reads what that person is allowed to read, in the project and in the Knowledge Hub.
Yes. Every access change is on record with the person who made it and when.
Yes. A dashboard can stay private, be shared with specific people or teams, or with the whole company.