Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time
---
title: "Your first person"
teaching: 0
exercises: 20
questions:
- "Question here"
objectives:
- "List the objectives"
keypoints:
- "List the key takeaways for the episode"
---
# Your first person!
![Interactive system activity](/assets/img/hands-on-keyboard.png)
You have installed COmanage; the first person is created during this process. By default, this person holds the role of Platform Administrator. We will use this person to explore some of the concepts that we have learned about, and see how COmanage expresses them.
We won't be changing this person. You will create a record for yourself in a later lesson.
## About Platform (CMP) Administrators _(aka Registry Admins)_
Platform Administrators are effectively super users, with the ability to perform almost all operations on the platform.
# Sign into the Registry
1. Using the credentials you specified as part of the COmanage setup, sign into the system. These credentials have Platform Administrator privileges.
# View the `Org Identity` Object :gear:
_It might make sense to swap the order here. The CO Person is the primary object, and maybe it should be explained first?_
1. Click on the upper right corner of the screen to expand the user menu.
2. From the menu, select the Organizational Identity shown. This action will open the Organization Identity in "view" mode.
![screen shot - select the Org Identity from the user menu](/assets/img/05-OpenOrgIdentity.png)
3. Explore the attributes and associated items that we talked about:
* Name and affiliation
* Linked Identifiers
* Lists of email addresses
* Linked `CO Person`:gear:
4. Click on the Edit button to get a feel for the experience of changing attributes. This experience is similar to the **Self Service** experience that may be enabled for some users.
* Try adding another name - notice what it looks like when saved, for example, one of these names is designated as the "primary" name.
* Add an email address
# View the connected `CO Person`:gear: object
1. Click on the "view" button next to the `CO Person`:gear: object to view the object. (you can do this from the view or edit screens of the `Org Identity`:gear:)
![screen shot - view the connected CO Person object](/assets/img/05-ViewCOPerson.png)
2. Explore the attributes and associated items that we talked about. Notice the differences between the things connected to the `Org Identity`:gear: and the `CO Person`:gear:
* Name and affiliation
* Linked Identifiers
* Lists of email addresses
* Status
3. Notice the groups that this `CO Person` was automatically assigned to. We will talk about groups in the next lesson.
# Restore things
Before we move onto the next lesson, restore any changes that you may have made, particularly in adding names or email addresses. This action will help ensure that we all have similar experiences when doing the next set of hands on activities.
---
PREVIOUS SECTION: [4. Permissions](/_episodes/04-permissions.md)
LESSON OVERVIEW: [CO310 - Modeling People in COmanage](../index.md)
---
NEXT LESSON: [CO320 - Modeling Your Organization in COmanage](https://github.internet2.edu/lpaglione/COmg-CO320-modelOrg/blob/master/index.md)
WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)