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

A2. It indicates that your role doesn't have the privilege of concerned project settings. Please reach out to your Asite administrator to request access if needed.

A1. A role can only be deleted if no user, role, or organization has ever been assigned. For a role that is/was assigned to any user, role, or organization, the role name is allowed to be edited. Also, the users, user groups, or organizations in such roles can be added or removed as and when required.

A2. This can happen in projects cloned from templates with the inheritance option enabled.

Click here to learn how to manage user roles and access in a project template.

Click here to understand how to break the inheritance of workspace objects.
​

A1. Such a user will get a combination of privileges based on each of the roles assigned to them.

A2. It can happen in projects cloned from templates with the inheritance option enabled.

Click here to learn how to manage role privileges in a project template.

Click here to understand how to break the inheritance of workspace objects (if required).

A1. Such a user will get a combination of form permissions based on each of the roles they are assigned to.

A2. This can happen in projects cloned from templates with the inheritance option enabled.

Click here to learn how to manage form permissions in a project template.
Click here to understand how to break the inheritance of workspace objects.

A1. Please check that the required project is selected in the project filter where proxy access was assigned. If it still does not appear, you can check if you are accessing outside the selected start and end dates for proxy access.

A1. 'Basic' form templates are hard-coded and cannot be customized, while 'Custom' form templates can be completely customized as and when required.

A2. You can assign the same form template multiple times in a project as required. Every form template added to the project should be configured with a unique AppBuilder FormID Code for quick identification and better management of project form templates.

A1. Please publish the form template again. Choose a template file (.xsn / .zip) by clicking the 'Choose File' button, and the option for 'Multiple Response' will be accessible.

A2. This can happen in projects cloned from templates with the inheritance option enabled.

If so, go to the relevant project template from which the project was cloned. Then, deactivate the concerned form types.

Click here for detailed help on how to break the inheritance of workspace objects.

A3. The 'Type' column in the 'Projects' area displays whether the corresponding record is an 'Independent' project, a 'Cloned' project, or a 'Template'.

In the case of a 'Cloned' project, the 'Cloned From' column corresponding to that particular project in the projects listing screen displays the template name from which it was cloned.

If the required columns are not visible in the listing, see how to customize columns in a listing area.

A1. You can edit a form status or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access to the corresponding form status. Please speak with your Asite administrator to request access if needed.

A2. All deactivated form statuses will appear in italic font when managing form statuses. To reactivate a form status, untick the 'Deactivate' option against the same and click 'Save'.

A3. The colour shades for statuses are determined based on whether the status is active/inactive and formatted / not formatted. Accordingly, the gear icon for a given status can contain shades of grey or black.

A4. This can happen in projects cloned from templates with the inheritance option enabled. You need to go to the template from which that project is cloned and manage form statuses within that template.

Click here for detailed help on how to break the inheritance of workspace objects if needed.​

A5. The 'Type' column in the 'Projects' area displays whether the corresponding record is an 'Independent' project, a 'Cloned' project, or a 'Template'.

In the case of a 'Cloned' project, the 'Cloned From' column corresponding to that particular project in the projects listing screen displays the template name from which it was cloned.

If the required columns are not visible in the listing, see how to customize columns in a listing area.

A1. You can edit a value or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access to the corresponding POI. Please speak with your Asite administrator to request access if needed.

A2. All deactivated POIs will show in italic font. To reactivate a purpose of issue, untick the 'Deactivate' option against the same and click 'Save'.

A3. This can happen in projects cloned from templates with the inheritance option enabled. You need to go to the template from which that project is cloned and manage POIs in that template.

Click here to learn how to manage POIs in a project template.

Click here to learn how to break the inheritance of workspace objects.

A1. You can edit a file status or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access to the corresponding file status. Please speak with your Asite administrator to request access if needed.

A2. All deactivated file statuses will show in italic font. To reactivate a file status, untick the 'Deactivate' option against the same and click 'Save'.

A3. The colour shades for statuses are determined based on whether the status is active/inactive and formatted / not formatted. Accordingly, the gear icon for a given status can contain shades of grey or black.

A4. This can happen in projects cloned from templates with the inheritance option enabled. You need to go to the template from which that project is cloned and manage file statuses in that template.

Click here to understand how to manage file statuses in a project template.

Click here for detailed help on how to break the inheritance of workspace objects if needed.

A5. The 'Type' column in the 'Projects' area displays whether the corresponding record is an 'Independent' project, a 'Cloned' project, or a 'Template'.

In the case of a 'Cloned' project, the 'Cloned From' column corresponding to that particular project in the projects listing screen displays the template name from which it was cloned.

If the required columns are not visible in the listing, see how to customize columns in a listing area.

A1. You can edit a distribution group, only if you have 'Admin' access on the same. Please speak with your Asite administrator to request access if needed.

A2. This can happen in projects cloned from templates with the inheritance option enabled. You need to go to the template from which that project is cloned and manage distribution groups in that template.

Click here to understand how to manage distribution groups in a project template.
Click here for detailed help on how to break the inheritance of workspace objects if needed.

A1. You can view the working calendar irrespective of the role you belong to. Based on the privileges assigned to your role, you can configure your working calendar while adding/editing a project.

A1. You can clone a project template by specifying the objects you want to clone and keeping the inheritance option off. This will clone the existing project structure only, without having any subsequent updates from the template.

A2. Click here to understand how to create a new project.

A1. A working calendar defined on your project helps calculate the due date for any task distribution. This can be based on the number of days the user defines in various scenarios. A typical distribution task wouldn't apply to a past date. Hence, holidays for past dates in the working calendar are not allowed.

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

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

A1. A working calendar defined on your project helps calculate the due date for any task distribution. This can be based on the number of days the user defines in various scenarios. A typical distribution task wouldn't apply to a past date. Hence, holidays for past dates in the working calendar are not allowed.

A2. It is displayed in the 'Cloned From' column corresponding to that project. If you don't see this column in the projects listing, add the same field from the available fields using the option for customizing columns.

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

A1. It is displayed in the 'Cloned From' column corresponding to that project. If you don't see this column in the projects listing, add the same field from the available fields using the option for customizing columns.

A2. No. Breaking the folder's inheritance will require breaking the inheritance of dependent objects which can include folder permissions, workflow definitions, workflow system tasks, etc...

Suppose a change in folder configuration is specifically required on a project. In that case, you can create a new folder with the configuration needed for that project.

Suppose a similar configuration is required for the other projects. In that case, it is best to communicate the general configuration to the relevant project manager and update it directly on related project templates so that all projects can benefit from it.

A1. You must know the email address associated with the project folder to which you want to send/publish the email. If you send an email to that email address, it will be automatically published in the concerned project folder if the mailbox is active.

A2. We currently don't support emailing multiple project mailbox addresses simultaneously. However, according to the mailbox configuration, you can always send separate emails to each project mailbox address.

To ensure optimum utilization of available storage space and avoid data duplication, it is advisable not to save the same content at multiple project locations. To achieve your purpose when the same file or email content reference needs to be placed at various project locations, Asite lets you link files from one project folder to another, within the same or other projects accessible to you. Click here to learn more.

A3. You can find the details of the user who sent the email within the file content.

A4. Once assigned, an email address cannot be changed for a particular configuration. You can go ahead and deactivate the current configuration and create a new configuration with the email address you need.

A5. There is no clear or specific way to find if a file was published via mailbox. If you have any relevant information regarding the files published via mailbox, you can use different options like search and filters within the 'Files' tab to help identify such files.

A1. Once assigned, an email address cannot be changed for a particular configuration. You can go ahead and deactivate the current configuration and create a new configuration with the email address you need.