Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Overview

Request Access Workflow allows you to configure the Request Access option on CAM web UI. Configure-Request Access option through request workflow. It enables you to access any MS Team with or without approval based on your configuration.

Prerequisite

  • You need to assign a Role to view the Request Access option on CAM web UI. For more information on Configuring Permissions in CAM, click here

  • You need to assign a Role to access the Team Request Access option on CAM Team App. For more information on Configuring Permissions in CAM, click here

Configure-Request Workflow for MS Teams

  1. Navigate to Administrator

  2. Click Request Workflow Configuration

  3. The Following screen opens where you can customize the following operation:

    1. View the added dialog list

    2. Configuring Request Workflow

    3. Configuring Request Workflow in Desksite

Add New Dialog for MS Teams

Allows you to configure new new dialog.

  1. Click New Dialog, the following screen opens:

Field

Description

Dialog Name

Enter the name for the workspace dialog.

Note: The label that is displayed at the top of the dialog.

Set as Default

Select Yes to set the workspace dialog configuration as the default configuration based on Action Type to be applied to all workspaces.

E.g. User can set a default dialog for Create Workspace and another default dialog for Create Team action type and so on.

System

Select the external system as Office365 from the list to use for this dialog.

Action Type

Select the type as Request Access of the wizard from the dropdown.

  1. Click Next to create the new dialog

Note: User can customize the dialog details in the provided accordion. For more information on Customizing the dialog accordions see Configure Request Workflow Customizing-the-dialog-accordions

Important: To create MS Team workspace through Request Access, you need to configure the Office365Team unique metadata.

Configuring Unique Metadata

  • Allows you to add unique metadata to the workspace dialog created here. This metadata is displayed in the selected panel

  • Click the Add New button in the far right column to assign unique metadata to the panel. In the Add Unique Metadata window, the following dialog opens -

Fields

Description

Metadata

Select the Metadata value as CreateInOffice365 from the dropdown list.

Default Value

Enter the default value to be assigned to the metadata value.

Is Hidden

Select the Hidden status value.

Is Read Only

Select the read only value.

Display Label

Enter a display name for the metadata. Make this as specific as needed to differentiate between similar metadata names that may exist.

Help Text

Enter help text to be displayed as a tool-tip on the custom field.

Type

Select the type of metadata from the drop-down. Options include:

  • Date: Represents date value (e.g. 2018-10-10)

  • String: Alphanumeric characters (e.g. cam123)

  • Boolean: Represent logical values (e.g. True or False)

  • Number: Numeric data values (e.g. 1,2,3)

  • Currency: Represents integer format (e.g. 123.456)

Look Up

By default Look up value is No for selected metadata value.

Order

Set the order of the metadata to be displayed on the panel.

Panel

Select the panel for the metadata to be displayed. Based on the selection here the fields will be displayed in the panel.

Editable

Select Yes to allow the metadata value to be edited in the workspace dialog.

Lock Existing Values

This option doesn't allow users to create a new workspace using previously added values of specific metadata, locking the existing metadata.

When a new Unique Metadata field in Configure Wizard is added, the option to Lock Existing Values displays. If Lock Existing Values is selected as YesCreate a new value option should be automatically selected as Yes. The option No should be disabled. Also, the Default Value option is disabled.

If the Metadata with Lock Existing Values option is 'No', then users can only add values to Metadata by clicking the '+' button. After the user enters values for that Metadata, there is a validation to check if that value already exists. If the value already exists, the user should not be able to save that value.

E.g. Lock existing set to yes and is parent set to yes, means the unique metadata field matter will not allow inputting duplicate matters if any parent matters exist. If no for parent, and yes for lock, then if the metadata exists in entire system, then the value can't be added.

  • Click Save to add unique metadata or click Cancel to close the dialog

Viewing Request Access on CAM UI

  • After the request workflow is configured, launch the request workflow to access an option Request Access in the configured external system.

  • Click the plus sign on the top-right corner of the screen.

Note: The workspace drop-down dialog is displayed, if there are more than one workspace dialog configured in the workspace wizard configuration.

Removing Access from a Team

The "Office365TeamIdCollection" metadata allows for better management of a user in a team. For example, if the metadata flag is set to true, then the logged-in user’s teams that he/she is a member of will display in the lookups in Request Workflow.

  • A check has been added so that if the user is in the CAM Admin role, they can see all Teams. This will allow CAM Admins to remove users from Teams where they are not members.

  • The wizard will present the list of team members in the Security panel, based on the team selected from the drop-down list, whether the user is an external user or not.

  • A request can go for approval to designated approvers if that is configured in the workflow, or simply submit the job into CAM if the user does not require approval.

  • There is an option to Add/Remove users with admin roles as: Yes/No

  • If the users are accidentally removed, then you can add them back to the team

To remove access:

  1. Add the Office365TeamIdCollection metadata on the configuration of the request workflow for the Remove access wizard

  2. When the user adds the Office365TeamIdCollection, it will show the Teams based on the client and matter ( Client and Matter is a required field to view any team)

  3. The user is part of that team or should be a user with permission (allowed Workspace Search As Admin) to view the team
    If Workspace Search As Admin is allowed you can view any team even if you are not part of that team
    If Workspace Search As Admin is Deny but you are part of that team still you are able to see that team.

  4. On the Remove access wizard when the user selects the Team from the lookup on the Next dialog the team members will be present in the Security panel

  5. If we have approvers in the wizard the request workflow ( workspace ) needs to be approved by the approver
    If we don’t have approvers in the wizard, the request workflow ( workspace ) does not require approval

Note: Keep the following in mind:

  • You will not be able to remove all admin users: at least 1 admin user is required in the team.

  • When you try to remove the last admin member from the list, a notification will be shown: "The Team must have at least one user with an Admin role. Please add at least one Admin user back to the Team."

  • Token Users are automatically populated on the member list and cannot be removed.

Accessing a Team

  • After creating MS Team workspace, navigate to CAM within MS Team

  • Navigate Directory > Click New Request drop down

  • Click Request Access to get an access to specific Team based on configured external system

  • Enter the name of the configured Team name.

  • Click Next, to navigate next screen

  • The configured Panel will be displayed with added user

  • Click Next, to navigate next screen

  • You can Review the configured Team and user.

  • Click Submit to access the MS Team with or without approval.

  • The Job will be completed successfully, your Team App is ready to access if no approval configured.

Note: If you set approver, the once you access a team, the request will send to approver, once approver approve a request then you can access the requested Team.

  • No labels