Projects FAQs

A1. Yes, you can do this from the project listing view. Select multiple projects, right-click, then choose the Mark as Favourite / Remove as Favourite option as needed.

A2. It’s because your role does not have the Edit Workspace Details privilege. Please reach out to your Asite administrator to request access if required.

A3. By default, all new projects come with the following roles:

- Field Administrator

- Field Contractor

- Field Inspector

- Workspace – Administrator

These system-defined roles cannot be edited or removed. (NOTE: for BIM-Enabled projects, you will have two additional system-defined roles [cBIM Publisher and cBIM Viewer]).

You can only delete a newly created role if it has no users, user groups or organisations assigned to it. To delete a role, click the delete ❌ icon next to its name. If the role has any users or organisations assigned, you can’t delete it (however, you can rename it instead).

You can add or remove users, user groups, and organisations from any role at any time.

A4. This usually happens when your project is cloned from a template with the inheritance option enabled. Inherited items can only be managed from the original template.

To make changes:

Examples of items this can affect:

A5. A user will get a combined set of privileges or permissions from all the roles assigned to them.

A6. Ensure the selected project (displayed via the project filter) carries the proxy access assigned. If this is the case and the user’s name still doesn’t appear, confirm that you are accessing their account within the allocated start and end dates of the proxy access.

A7. Basic form templates are hard-coded and cannot be customised, while Custom form templates can be completely customised whenever required.

A8. You can assign the same form template multiple times in a project as required. Every form template added to the project must be configured with a unique AppBuilder Form ID Code.

A9. Reselect the form by clicking Choose File and picking a valid .zip template. Once the file is selected, (before clicking Upload), the Multiple Response option will unlock. Once selected, click Upload.

A10. You can edit or deactivate these items if you have Admin access to them. If you don't have Admin access, contact your Asite administrator to request the necessary permissions.

A11. The working calendar tells the system which days count as working days. When you set a task deadline, the calendar skips any non-working days you've defined (such as weekends or personal holidays) and calculates the due date accordingly.

Because due dates are always forward-looking, you can only add holidays for future dates. Holidays in the past won't affect task deadlines, so they can't be added.

A12. Only users with the Edit Workspace Details privilege can edit the working calendar. Click here for more information on how to add a holiday to the working calendar.

A13. The QR code functionality is currently supported only in the PDF file format. Click here to understand how to use QR code functionality on files created in other formats.

A14. It is displayed in the Cloned From column corresponding to that project. If you don't see this column in the projects listing, refer to this article on Project Navigation for more information on how to restructure your columns.

A15. No. Inheritance is what keeps your cloned project in sync with the original template. It covers folders, permissions, workflows, and system tasks. Because these are linked, you can't break inheritance on a single folder; breaking it would cascade other areas, and once broken it cannot be restored.

Instead:

A16. On the Asite platform, text shown in italics means the item is inactive. This helps you quickly distinguish between active and deactivated elements in your workspace.

Items that will appear in italics when deactivated include:

To reactivate a Form Status, File Status or Purpose of Issue (POI):

To reactivate a Workflow Definition(s), Workflow Trigger(s) or System Task(s):

A17. Click here to understand how to create a new project without using a template.

A18. The colour of the cog ⚙ icon indicates whether status formatting has been customised:

A19. Only users with Admin permissions can edit distribution groups. Please speak with your Asite administrator to request access if needed.

A20. No, a project cannot be deleted once it has been created. However, you can change the project status depending on your access. Click here to understand more about project statuses.

A21. We currently don't support emailing multiple project mailbox addresses simultaneously; however, you can send separate emails to each project mailbox address.

A22. You can find all relevant details of the user who sent the email by simply opening the file.

A23. Once assigned, a project mailbox address cannot be changed. Alternatively, you can deactivate the current project mailbox configuration and create a new one with the email address you need.

A24. You must know the email address associated with the desired project folder. If the mailbox is active, once you send an email to that email address, it will be automatically published in the concerned project folder.

A25. While there are no attributes or metadata to identify a file published via the project mailbox, you can confirm it by checking the file's history:

In the expanded view, the Remarks column reflects "Emailed into workspace" if the file was published through the project mailbox.