Outside access
Let a client or a contractor in without showing them the company
Two built-in roles for people who are not on your payroll. The client, who watches their own project and changes nothing. The invited contractor, who works on theirs — logs hours, moves tasks — and never sees a second project or a single name from your team.
Granting access is easy. Granting ONLY that access is the job.
A freelancer comes in for three months. A subcontractor puts two people on a site. A client asks every Friday how their work is going. In most tools the answer is the same either way: open them a full account and they see the whole board, or open them nothing and email a PDF by hand every week.
The first shows what it should not — your other clients, your headcount, what each person costs. The second is your Friday afternoon, every week, and it always arrives after the question. Fichaloto splits that choice into two roles, and fences each one with a different mechanism, because each one has a different problem.
The client: sees their own work, and only looks at it
The Client role is born fenced. Whatever permissions you hand it, it only ever sees the projects ticked on that person's record, and with an empty list it sees none. That is the safe position until somebody deliberately fills it in.
And it is read-only, with no exceptions: nothing written, nothing corrected, nothing deleted, no card dragged across a timeline by accident. What they get is the project and the work inside it.
- Not your people, not your rates — who is working on the project and what their hour costs is your business, not the business of whoever pays the invoice.
- No margins, no reports, no invoicing, no API — and that is a decision, not an oversight: those screens still read per account rather than per project, so handing over the permission would hand over everybody else's margin too. They go in when they are fenced.
- None of your other clients — the account boundary stays exactly where it was, and the ticked project list sits on top of it.
The contractor: works on theirs, and on nothing else
The Project contractor role is for the person invited in from one specific piece of work. It resembles the client in that they only see their own projects, and in nothing else: the client watches, the contractor works.
They log their hours, move their tasks across the board, request time off and clock in if the account runs time tracking. What they do not do is create tasks, rename them or shift a due date. The plan belongs to whoever runs the project.
Their lock lives on each person's project list, not on the role, and that distinction is the whole design. If it lived on the role, a hundred contractors would share one list and every one of them would see the others' work. One role plus a list per person means inviting contractor number one hundred and one shows them nothing about the hundred before.
Inviting somebody is not an admin job
Whoever runs the project invites from the project, without opening people administration and without asking anyone to do it for them. It takes the invite permission, which already ships with every role that could create and correct projects.
An email goes out with a link that lives seven days, in the language of the person receiving it rather than the language of the person sending it — it is the first thing they ever read from Fichaloto, and sending it in a language they do not read is a poor start. They open it, choose a password and land straight on the project they were invited to.
Both doors into Fichaloto — a person's record and an invitation from a project — seal the same token, with the same expiry, leaving the same line in the audit trail. And every email that goes out is logged: who it went to, what the subject was and whether it left.
And when they leave
Take the project off a contractor and there is nothing left for them to see. That is the whole offboarding: no account to delete, nothing to remember to revoke somewhere else. The hours they logged while they were here stay exactly where they are, counting in the project and in its reports. Somebody leaving should not put a hole in your history.
Frequently asked questions
Can a contractor see the people in my company?
No. They see the project they were invited to and the work inside it. The team screen is not in their role, so no headcount, no job titles and certainly no hourly cost for anybody.
Can I invite the same person to two projects?
Yes. The project list is per person, so you add as many as you need and they see those. Remove one and they lose that one and keep the rest.
How long does the invitation link last?
Seven days. After that the link stops working and you invite again, which is one click. It is the same window as a normal joiner.
Do contractors count towards the people on my plan?
They are people in your account, so yes, they take a seat. What they do not do is force you into extra modules: a contractor on the base product works perfectly well.
Can a client download their own project data?
They get the project screens and the work inside them. Exports and the API sit outside the role on purpose, because today they read per account rather than per project. If a client needs a file, you export it and send it.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.