Describe LCS project and project user roles
X++ Programming Language > Implement Lifecycle Services (LCS) tools > Implement Lifecycle Services (LCS) tools
667
Answer:
Describe LCS project and project user roles
Projects
This article provides information about projects in Microsoft Dynamics Lifecycle Services (LCS). It describes some important features and also explains the role of the project methodology.
Projects are the main organizer of your experience in LCS. The methodology that is associated with a project determines the default phases and tasks that are included in that project.
Key features
Feature |
Description |
Invite who you want. |
Customers and partners can invite each other to participate in projects. You also can invite prospects. If you use Cloud-powered support, you can also invite Microsoft support engineers. |
Change ownership. |
You can change the ownership of a project as you require. For example, you can change the ownership from a partner to a customer, or to a different person at a customer. |
You must follow the methodology in your implementation project. The methodology framework is designed to guide you through the implementation. As you perform actions in LCS, you can begin to mark the phases and tasks as completed. Locked methodology tasks can be marked as completed after you complete the prerequisite. You can click the lock icon to learn what you must complete before you can mark a task as completed. As you work through the phases and tasks in the methodology, environments become available for you to configure.
Delete a project
When you have LCS opened, you have a view on recent projects. Click the option All projects. You then have a view of all projects in a list style. Select a project and click the Trashbin icon. The project with all related information will be deleted.
Configure Lifecycle Services (LCS) security
Security in Microsoft Dynamics Lifecycle Services (LCS) is controlled at both the organization level and the project level. Not all members of an organization have access to all projects. Additionally, the members of a project might not all be members of the same organization.
Currently, users can sign in by using the Microsoft Azure Active Directory (Azure AD) credentials that they created in the Microsoft 365 portal when they signed up. Users who are administrators for their organization in Azure AD will be administrators in Lifecycle Services (LCS).
Project-level access to LCS is by invitation. You can invite members of your organization to be project owners and team members. Additionally, you can invite users who aren't part of your organization, and who don't have accounts in Azure AD to be team members.
Manage LCS organization users
Only an administrator can manage users. Follow these steps.
-
In PartnerSource Business Center (PSBC) or Azure AD, associate all the users in your organization who require access to LCS with your organization. Users might have to wait up to two business days before they can sign in to LCS.
-
Add your users to the appropriate projects in LCS.
Invite a user to an LCS project
-
Sign in to LCS.
-
Select the project to add the user to.
-
Select the Project users tile, and then, on the Project users page, select the plus sign (+).
-
Enter the user's email address, select the correct security role, and then select Invite.
Configuring project security
You can invite users from inside or outside your organization to join your project as users. The following table describes the roles that are available for users.
Role |
Description |
Project owner |
Members of this role have access to all tools in LCS, can add other users in any role, and can delete the project. |
Environment manager |
Members of this role have access to all tools in LCS and can manage cloud-hosted environments. |
Project team member |
Members of this role have access to all tools in LCS but can't manage cloud-hosted environments. |
Project team member (prospect) |
Members of this role have limited access to all tools in an LCS project. Prospects are users who have been added to a project, but who don't have an account in VOICE or an Azure AD account. You can identify that a user is a prospect because prospect is listed as the organization. |
Operations user |
Members of this role have access to the following tools in LCS:
|
After you've configured security for one project, you can import the users to another project.
Configure implementation roles
If you have an implementation project, you will have the option to specify project user's implementation roles.
This Particular section is dedicated to Question & Answer only. If you want learn more about X++ Programming Language. Then you can visit below links to get more depth on this subject.
Join Our telegram group to ask Questions
Click below button to join our groups.