CloudScaff questions and answers

Users permissions and customer access

Answers to 10 questions about users permissions and customer access.

← All FAQ topics

10 questions

Questions in this topic

10 answers
How many users can we add?

CloudScaff includes unlimited users. You can give the people involved in your operation their own access instead of restricting participation to a small number of office accounts.

Access is still controlled through permissions and site assignments. An unlimited-user model does not mean every person sees the same information or has authority to approve inventory movements, change records, or administer the account.

Can different people have different permissions?

Yes. Roles control the functions and actions available to users. You can configure access around responsibilities such as administration, inventory control, site supervision, inspections, or customer visibility.

Decide who may view, create, update, submit, approve, or complete each relevant workflow. That helps the system reflect the way responsibility is divided in your business instead of relying on informal instructions about which buttons people should avoid.

Can site staff be restricted to their own projects?

Yes. Site access can be limited to the projects assigned to a user. A person working on one job does not need to see every project in the business.

This is useful for both internal teams and external users. Check the user's role as well as the site assignment, because project visibility and permission to perform an action are separate parts of the setup.

Can we create our own roles?

Yes. The role builder allows you to configure permissions around your responsibilities and job titles. You might create roles for a leading hand, yard controller, operations manager, inspector, or customer representative.

Test each role using a representative user before assigning it widely. Confirm that the person can complete the intended workflow and that they cannot access unrelated functions or projects.

Can someone view information without changing it?

Yes. You can provide viewing access while withholding the permissions required to edit or complete actions. This is useful when a manager, customer, or contractor needs visibility but does not own the underlying workflow.

For example, a customer might need to see a scaffold register or project inventory without being able to change stock balances or dismantle a scaffold record.

Can we give customers access to their own projects?

Yes. Customer access can be configured so customers see the projects and information you choose to share. This can reduce repeated requests for documents or updates that are already recorded in the system.

Decide what the customer needs to do before creating the role. Viewing a register, reviewing site inventory, and signing a handover are different requirements and should be configured deliberately.

Can we hide inventory management from people who only inspect scaffolds?

Yes. Permissions can limit users to the tools relevant to their responsibilities. An inspector does not need broad inventory administration access simply to work with scaffold records.

The same principle applies in reverse: yard staff can focus on inventory workflows without needing to manage inspections. This keeps the working interface more relevant and reduces the chance of unrelated changes.

Can we restrict who approves stock movements and adjustments?

Yes. Configure roles so that the appropriate people control approval and completion actions. A site user can have a request-focused role while an inventory controller manages the subsequent stock process.

Use particular care with immediate-completion actions and balance adjustments. The person performing those actions should understand when stock becomes recorded as delivered, returned, or available again.

Can permissions change as our team changes?

Yes. Roles and user access can be updated as responsibilities change or additional workflows are introduced.

Review permissions when someone changes position, leaves a project, or no longer needs customer access. After a change, check a representative workflow from that user's perspective so the new access is both sufficient and appropriately limited.

Should our team share one login?

Use individual accounts wherever practical. A shared login makes it harder to distinguish who performed an action and can weaken the usefulness of the operational record.

Because CloudScaff includes unlimited users, each participant can have access suited to their responsibilities. If several people use a shared device, establish a clear sign-in process so activity is recorded under the appropriate person.

A real team, ready to help

Let’s talk about your operation.

Get help with a workflow or find out how CloudScaff fits your business.

Contact our team

Contact us

How can we help?