Controlled Access

Different teams see only what is relevant to them

Separate teams - but all on the same system

If there are multiple teams using Flowzone or you are working with clients, then Flowzone can create separate environments for each group.

Control which jobs or projects teams have access to and limit what they are able to see or do on each project.

Management perspective - see everything!

Even if you limit access or control access for other teams, you can still give management access to everything.

Controlling access within projects...

When users view a project they will only see limited information and not the full project details (if that's what is required).

You can control access to the different elements of a project...

All documents

Documents with a certain status

Certain project information

Project schedule

Project milestones

Project comments and events

Who is in the project team

In Flowzone you are able to control all of this and more!

Controlling what users do...

Along with controlling which projects a user has access to (and the information within that), you can control what users can do.

Can they create new projects, upload documents, add comments, create and edit activities?

With smaller teams you might allow everyone to do everything: keep it relatively simple.

But when you get working across multiple teams, you might want to turn off functions that just aren't going to be useful to people. Keep the system clean and simple for those users.

Control with Flowzone

Enable or restrict what different teams can do.

Try Flowzone

See also...