Your team, and what each person can do

Roles are permissions in a bundle; invite once, and the right screens appear.

In this lesson

The roster

Dina owns the studio, so the people side of Taskity is hers. Everyone you will meet in these lessons works for her, and each one sees a different product.

One row per person, with the role they hold next to their name. Youssef runs the jobs, Tarek is on site, Hoda buys, Mostafa values and invoices, and Salma designs.

What a role actually is

A role is not a job title here. It is a bundle of permissions — the screens you can open and the things you can change. Give someone the wrong one and they either see too much, or cannot do their day’s work.

The permission matrix

The matrix makes that explicit. Every role, down the side; every part of the product, across the top.

This is the reason the site engineer never sees the finance screens. It is not a bug and it is not a restriction he outgrows — it is how a fit-out firm keeps one team out of another team’s numbers.

The audit trail

Behind every change sits an audit trail: who did what, and when. When a rate moves, or a card changes hands, this is where you prove it.

Inviting someone

To add a person, invite them by email and pick the role once. There is nothing else to configure.

She joins with exactly the access her role carries — no more, and no less. You will not be adjusting permissions one screen at a time for the next year.

The habit that matters

One habit for the studio owner: decide the role before you send the invite. A person invited as an Owner can see every number in the business, and that is not a thing to fix later by phone.

What just happened

  1. The roster

    Dina owns the studio, so the people side of Taskity is hers. Everyone you will meet in these lessons works for her, and each one sees a different product.

  2. What a role actually is

    A role is not a job title here. It is a bundle of permissions — the screens you can open and the things you can change. Give someone the wrong one and they either see too much, or cannot do their day’s work.

  3. The permission matrix

    The matrix makes that explicit. Every role, down the side; every part of the product, across the top.

  4. The audit trail

    Behind every change sits an audit trail: who did what, and when. When a rate moves, or a card changes hands, this is where you prove it.

  5. Inviting someone

    To add a person, invite them by email and pick the role once. There is nothing else to configure.

  6. The habit that matters

    One habit for the studio owner: decide the role before you send the invite. A person invited as an Owner can see every number in the business, and that is not a thing to fix later by phone.

Open team Opens Taskity in your own project.

Next: Turning modules on and off →

Put it into practice.

Boards, approvals, snags and client sign-offs — one platform your team will actually use.

fitdatum.com