< Previous | Next >

Lesson 2: Assign users to a community

In this lesson, you will give "signed-in" users access to browse and download assets in a sample community named Repository Configuration. The users must be signed in to the repository in order for you to add all "signed-in" users to a community. You will give only a few users permission to upload or create assets. All users will be able to read and review the assets.
You can create communities to keep similar assets for certain projects organized by group, or to define collaborative workspaces for many departments. In each community, you can define users or user groups to interact with specific permission levels depending on the role of the user or user group. Lifecycles and review policies are also defined in communities and are usually focused on specific asset types and repository categories.

To open and add the consumer role to the signed-in users in the community:

  1. Click Administration. This opens the list of the sample communities shipped with the SOA model.
  2. From the list of available sample communities, click Sample Application Development.
  3. On the Users tab, click the Edit roles link that corresponds to the Signed-in users.
  4. In the Find User and Assign Roles window, select the Asset Consumer check box.
  5. Click Finish to add the role to the user.

    Confirm that your Sample Application Development community has Signed-in users with the Asset Consumer role.

    Now, every user that signs in to IBM® Rational® Asset Manager will be able to find, view, download, and subscribe to assets in the Sample Application Development community.

  6. Click the Communities breadcrumb, or click Administration to return to the list of communities.
Remember: All users who are signed in to the repository act as a single user in the application. Unlike user groups in the repository, there is no way to assign different roles to different users.

To learn more about roles, see an overview on roles and permissions.

When working in your own repository, you will want to create a general community that defines repository processes and policies, and grant all signed-in users access to this community. This gives you, as an administrator, control over the directive information that is included in the policy and process assets. This is a best practice to ensure that all registered users have access to assets that are related to policies and procedures for using the repository. Then, as you define the best use practices for the repository, all registered users will have access the information.

Lesson checkpoint

In this lesson, you learned that strategists of asset-based development with Rational Asset Manager encourage you to create a community that gives all signed-in users browse and download access to the assets in the community that describe how a sample organization might use Rational Asset Manager to create software.
In this lesson, you learned how to perform the following tasks:
  • Add a role to users in a community.
  • Add permissions to roles in a community.
< Previous | Next >

Feedback