CONTROLLED ACCESS

Flowzone stores a wealth of information and documents about your projects.

Separate teams

If you are working in a smaller team, where you are happy to share anything, you might not need to control access.

Everyone would see everything.

However, if there are multiple teams or you are working with external parties, then you will usually want to use Flowzone's power to create separate environments.

Each team would not see the other's work.

Management perspective

If you do separate out access to other teams' work you will still, usually, have some people who, from a management perspective, will have access to all of the work across all teams.

Working with 3rd parties, clients and suppliers

The same thing would apply if you are working with people outside of your organisation. If you give access to your Flowzone system to suppliers or clients, then it is almost certain that you will want to control what they can see.

Controlling access to individual projects

The first level of access restriction is whether a user or group of users can access any given project.

You can allow access on an ad-hoc basis within each project via the user access list.

Or, Flowzone can add users in on a consistent basis depending on what type of project it is.

Controlling access within projects

When users view a project to which they have access, they may only see limited information and not the full project details if that's what is required.

You might want to hide...

  • all documents
  • documents with a certain status
  • certain project information
  • project schedule
  • project milestones
  • project time
  • project comments and events
  • who is in the project team

In Flowzone you have the ability to control all of this.

Controlling what users do

Along with controlling what 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?

Again, with small 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 nice and clean for those users.

Flowzone gives you fine-grained control. You can keep it really simple with relatively open access. Or - if you need to add in some levels of control - you have that capability, so that each user gets to see everything that you want them to see but no more.

Flowzone gives you fine-grained control. You can keep it really simple with relatively open access. Or - if you need to add in some levels of control - you have that capability, so that each user gets to see everything that you want them to see but no more.