CloudScaff questions and answers
Documents notifications and support
Answers to 16 questions about documents notifications and support.
16 questions
Questions in this topic
16 answersWhat kinds of files can we attach to records?
CloudScaff supports attachments such as images, videos, and PDFs for relevant operational records. These can provide context for a delivery, return, inspection, or handover.
Use a file type and size appropriate to the people opening it, especially on mobile connections. If your workflow depends on a specialist format or very large files, confirm the current limits and viewing behaviour before making it part of the process.
Is uploading a file the same as importing its data?
No. An attachment preserves a file as supporting information. An import reads structured data into the relevant system records.
For example, attaching an Excel material list to a delivery does not necessarily populate the delivery quantities. Use the supported import process when you want the items and quantities entered, and use attachments when you want people to view the original reference document.
Where should we store a document that applies to the whole site?
Use the appropriate site-level storage or documentation area for material that applies across the project. Attach a document to an individual scaffold or movement when it specifically explains that record.
A consistent filing approach makes information easier to find. Use clear names and avoid relying on several differently named copies of the same document spread across unrelated records.
Can our team use paper pick lists during the transition?
Yes. A team can use generated paperwork for the physical picking or counting task while the responsible user maintains the digital record.
Agree when the quantities are entered and who confirms the final result. A paper-assisted workflow can work well, provided the completed system record reflects the actual movement and the paper does not become a separate, conflicting stock ledger.
Can users receive notifications about work that needs attention?
Yes. CloudScaff uses notifications and pending-action indicators to help users see relevant activity. Notifications are associated with permissions, responsibilities, and operational events.
Set up the intended recipients and test the actual devices used by the team. Alerts should help someone complete a task; they work best when the team also understands who owns each step of the workflow.
Can notifications be limited to the right people?
Notification access can be aligned with user roles and responsibilities. This helps keep an inventory controller's alerts different from those needed by a site user or manager.
Review the configuration when roles change. If everyone receives every notification, important actions become harder to identify; if nobody receives the relevant alert, the workflow may stall without being noticed.
What should we check if someone is not receiving an expected alert?
Start with the user's role, site access, and the status of the underlying action. Check whether the event has actually reached the stage that should notify that user.
For device notifications, review the relevant browser or device permissions as well. If the issue continues, provide support with the user, project, action, and approximate time so the specific event can be investigated.
Is there an in-app chat function?
Yes. CloudScaff includes in-app chat to support communication around operational work.
Use conversation to clarify a question, but complete the formal action where it belongs. A chat message saying that equipment moved should not replace the transfer record, just as a message about an inspection should not substitute for the inspection record itself.
Why can one user see a button that another user cannot?
The users may have different roles, permissions, site assignments, or access to the relevant workflow stage. An administrator commonly sees more functions than a site user.
Check the intended responsibility before changing access. If the person should perform the action, review the specific permission and site assignment. Avoid granting broad administration access merely to make one missing button appear.
What should we do if a record appears not to have saved?
Check the record list and its current status before repeating the action. An operation may have completed even if the screen response was delayed.
Confirm your connection and review the relevant history where available. If the outcome remains unclear, contact support with the record details rather than repeatedly submitting a movement and risking a duplicate transaction.
What information helps support resolve a problem?
Provide the project or site, the affected document or item reference, what you were trying to do, what happened, and approximately when it occurred. A screenshot of the issue and the device and browser used can also help.
For a stock discrepancy, include the expected quantity and the movement you believe should explain it. Avoid sending passwords or unrelated sensitive information in a support message.
Where can we find help instructions?
The CloudScaff help centre contains product guidance, including system requirements and workflow documentation. It is a useful first stop when a user needs to understand a routine action.
If the instructions do not match your account or the problem concerns a specific transaction, contact the CloudScaff team with the relevant details. Live examples make a support conversation more productive.
Can new employees receive training after we have gone live?
Further training can be discussed as your team grows or responsibilities change. Use the employee's actual role as the starting point so the session covers the work they will perform.
For internal consistency, keep your own operating decisions clear too: who approves requests, when a delivery is sent, who counts returns, and how discrepancies are escalated. Product training and company procedure should reinforce each other.
Can we reopen a project that was closed?
The project workflow allows a closed site to be reopened when work resumes. Review its existing records and current stock position before creating new movements.
Reopening also needs to fit your active project capacity. If work has changed substantially, decide whether it belongs to the original job or should be represented as a separate project before entering transactions.
How much file storage is included?
Confirm the current storage allowance and any file-size limits for your account with CloudScaff. Your requirements will depend on the number of attachments, the kinds of files, and how long you need to retain them.
During evaluation, use realistic photographs and documents. A process based mainly on compact PDFs and a few clear images has different storage and upload needs from one that regularly captures long videos.
Can our IT team review security and access requirements before rollout?
Yes. Include your IT requirements in the evaluation so the team can review the proposed access and deployment arrangements before users are onboarded.
Bring specific requirements for identity providers, authentication, hosting location, backups, data retention, exports, and contractual commitments. Those details should be confirmed against the current service arrangements rather than inferred from the fact that the application is cloud-based.
No matching questions. Try another search or topic.