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

A2. The role you belong to, doesn't have the privilege for concerned project settings. You may contact your Asite administrator to request its access.

A1. A role can only be deleted if no user, role or organization were assigned to it ever. 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 that were cloned from project templates and having inheritance option turned on.

To understand how to manage users roles and access in any of your project templates, click here.

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

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

A2. This can happen in projects that were cloned from project templates and having inheritance option turned on.

To understand how to manage role privileges in any of your project templates, click here.

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

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

A2. This can happen in projects that were cloned from project templates and having inheritance option turned on.

To understand how to manage form permissions in any of your project templates, click here.

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

A1. You need to check that required project is selected in the project filter where proxy access was assigned. If it still doesn't appear, check whether you are trying to get access outside of the start and end date defined while assigning 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. Yes, you can assign same form template multiple times in a project as required. It is advisable that every form template added to the project be configured with a unique AppBuilder FormID Code for quick identification and better management of project form templates.

A1. To change the response type to 'Multiple Response', you need to publish the form template again. Select a template file (.xsn / .zip) file by clicking on the 'Choose File' button, and the option for 'Multiple Response' will be accessible to you.

A2. This can happen in projects that were cloned from project templates and having inheritance option turned on.

You need to find out relevant project template from which concerned project was cloned and then deactivate concerned form types within that specific project template as required.

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

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

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

In case you don't see the required columns in the projects area, click here to understand how to customize columns.

A1. You can edit an form status or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access on the same. You may contact your Asite administrator to request its access.

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

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

class

You need to find out relevant project template from which concerned project was cloned and then manage form statuses within that specific project template as required.

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

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

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

In case you don't see the required columns in the projects area, click here to understand how to customize columns.

A1. You can edit a purpose of issue or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access on the same. You may contact your Asite administrator to request its access.

A2. All deactivated purpose of issues 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 that were cloned from project templates and having inheritance option turned on.

To understand how to manage purpose of issues in any of your project templates, click here.

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

A1. You can edit a file status or use the 'Deactivate' checkbox against the same, only if you have 'Admin' access on the same. You may contact your Asite administrator to request its access.

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 color shades for statuses are determined based upon whether the status is active / inactive and formatted / not formatted. Accordingly, the gear icon for a given status can contain various shades of grey or black colors.

A4. This can happen in projects that were cloned from project templates and having inheritance option turned on.

You need to find out relevant project template from which concerned project was cloned and then manage file statuses within that specific project template as required.

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

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

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

In case you don't see the required columns in the 'Projects' area, click here to understand how to customize columns.

A1. You can edit a distribution group, only if you have 'Admin' access on the same. You may contact your Asite administrator to request its access.

A2. This can happen in projects that were cloned from project templates and having inheritance option turned on.

To understand how to manage purpose of issues in any of your project templates, click here.

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

A1. You can view working calendar irrespective of the role you belong to. Based upon the privileges assigned in the role you belong to, you can add / edit a holiday in working calendar directly while adding / editing a project.

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

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

A1. The primary purpose of working calendar is to enable automatic calculation of due date for any task distribution. This can be based on the number of days defined by the user in various scenarios, as applicable. A typical distribution task wouldn't be applicable for a past date, and hence defining holidays for past date in working calendar is not allowed.

A1. The QR code functionality is currently supported for PDF file format only by default. If you want to use QR code functionality with other file formats, see Extended QR Code on Files.

A1. The QR code functionality is currently supported for PDF file format only by default. If you want to use QR code functionality with other file formats, see Extended QR Code on Files.

A1. The primary purpose of working calendar is to enable automatic calculation of due date for any task distribution. This can be based on the number of days defined by the user in various scenarios, as applicable. A typical distribution task wouldn't be applicable for a past date, and hence defining holidays for past date in working calendar is not allowed.

A2. You can find this out from the 'Cloned From' column corresponding to that particular project in the projects listing screen. In case you don't see this column in the projects listing, add the same i.e. 'Cloned From' field from the available fields using the option for customizing columns.

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

A1. You can find this out from the 'Cloned From' column corresponding to that particular project in the projects listing screen. In case you don't see this column in the projects listing, add the same i.e. 'Cloned From' field from the available fields using the option for customizing columns.

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

However, if a change in folder configuration is specifically required on a project, it is suggested to create a new folder with required configuration in that project so that it serves your purpose.

If configuration is required in general for other projects as well, it is best to communicate to relevant project manager about general configuration and get it updated on related project template directly so that all projects can benefit out of it.

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

A2. We currently don't support sending an email to multiple project mailbox addresses at the same time. However, you can always send separate emails to each project mailbox address as per mailbox configuration.

To ensure optimum utilization of available storage space as well as to avoid duplication of data, it is advisable not to save same content at multiple project locations. To achieve your purpose when same file or email content reference needs to be placed at multiple project locations, Asite gives you an option to 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 actual user who had sent the email within the file content.

A4. Once assigned, an email address cannot be changed for a particular configuration. You can deactivate the current configuration and create a new configuration with the required email address based on availability.

A5. There is no clear or specific way to find out if a file was published via mailbox or not. If you have any relevant information available regarding the concerned files published via mailbox, you can use different options like search box 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 deactivate the current configuration and create a new configuration with the required email address based on availability.