Getting Started with the Federated Authorization FedAuth Community

1. Log in to the Federated Authorization Community.
2. Click one of the following tiles:
   • PeopleSoft
   • Student Mart
   • General Ledger (GL) Mart Users
   • General Ledger (GL) Mart Groups
   • Responsibility Center Administrator (RC Admin)
   • Employee Mart
   
    
3. Note: Approval Requests are handled below.
4. Enter all required information. If the form has multiple pages, fill each page out, then click Next Page. Click Submit.
5. Your access request is routed and—pending its approval(s)—is granted. You will receive an email message that indicates your request’s final status.
6. If you are an approver, you can see the comments in the Approval History list to see all the information about why your request was approved or not.
   Note: If a request for Federated Authorization resources is not approved, you can reapply making sure that your new submission satisfies all additional submission criteria.

This option is only available to those who can approve requests. All RC HR Approvers, RC Admins, RC Financial Approvers, and Security Contacts have access to all requests. Please reach out to your Approver for a status update on the request. If they are not able to give you an update, then contact the Technology Help Desk at 412-624-HELP (4357).

View your Pending Approvals

1. Log in to the Federated Authorization Community.
2. Click the Approval Requests tile.
3. If you are a member of an approving queue, such as a Security Contact, the approval list is divided into two sections with the top section showing your pending Federated Authorization requests. Click the Record link of an access request to view and manage information about it. The lower section contains a set of adjustable list views for Approval Requests of varying statuses and types and may include ones that are not pending action from you (for example, All Open GL Mart Requests).

Note: You can use the Search field to narrow your search to a single name or username.

Filter your Approval Requests

You can apply filters to look at specific groups of Approval Requests

1. Log in to the Federated Authorization Community.
2. Click the Approval Requests tile.
3. The approval lists is divided into two sections with the lower section showing a table that you can use to filter specific groups of Approval Requests. Click one of the downward-pointing arrowheads in the table headers ('v'), then make a selection from the drop-down list to apply a sorting filter to the table.
4. The Approval Stage for approved access requests will be listed as Approved, while those that still require authorization will be listed as Pending.
5. You can see the full history and comments in the Approval History list, including all the information about why your request was approved or not.

This option is only available to those who can approve requests. Approvers see requests based on their role(s). 

1. When you receive an email to approve a request, click the link provided, then log in to the Federated Authorization Community.
2. Click the Approval Requests tile.
3. In the My Pending Federated Authoization, click the Record link of an access request to view and manage information about it.
4. Review the Items to Approve section. Click View All to see more information about a specific item.
5. Review the details found in the right-hand column, including any (but not necessarily all) of the following:
   • Authorization Request
   • Career/Campus/Academic Center
   • Details of the Request
   • Division and Department Information
   • Requestor and Requestee Information
   • General Request Information
   • Restricted Data Requested
6. After completing your review, locate the Approval History section, then click Approve.
   
   For the entire request history so far, to view role/title, and to view or add comments to the request, click View All.
7. Type your comments then click Approve.
8. The process is repeated if additional approval for a request is needed.
   Note: All requests are routed to Information Technology for final approval.
9. The requestor receives an email notification when the request is granted and completed.

This option is only available to those who can deny requests. Approvers see requests based on their role(s). 

1. When you receive an email to approve a request, click the link provided, then log in to the Federated Authorization Community.
2. Click the Approval Requests tile.
3. Click the Record link for an access request.
4. Review the Items to Approve section. Click View All to see more information about a specific item.
5. Review the details found in the right-hand column, including any (but not necessarily all) of the following:
   • Authorization Request
   • Career/Campus/Academic Center
   • Details of the Request
   • Division and Department Information
   • Requestor and Requestee Information
   • General Request Information
   • Restricted Data Requested
6. After completing your review, locate the Approval History section, then click Reject.
7. Type your comments, then click Reject.
   
   Note: You can view any of your posted comments via the Approval History.
8. The requestor receives an email notification when the request is denied:

How are approval requests routed?

The following table identifies all the University administrators involved in approving your Federated Authorization Community requests:

What happens to a request when there are multiple approvers?

The request goes in to a queue and any approver can review, then accept or reject the request.

Are there steps that I can take as an approver to add information to my approvals?

In addition to adding comments, a site feature lets you post notes to the request using the Notes section.

How will I be notified about pending requests that require my approval?

You will get an automated email when the request is submitted and receive reminder messages containing the links to each approval request that is pending every Tuesday and Thursday.

Are there situations in which the use of adding additional documentation to an approval request is necessary?

Yes, additional documentation–including the use of comments and notes–is needed if an approval request for information is made outside the requestee's own RC.

Both All-Temps approval requests and Financial Data approval requests outside of your area fall under this category.

As an All-Temps employee, how is my Federated Authorization access request routed?

All Temps falls under RC 89 – Human Resources, so all Federated Authorization requests will be routed through the Security Contact(s) for RC 89. However, prior to officially submitting the request, the supervisor of an All Temps employee or the Security Contact of the department where the All Temps staff is assigned should discuss the access request details with the Security Contact for RC 89.

As a Security Contact, will I still receive a request to authorize a request that I have submitted?

Yes, the workflow determines that Security Contacts must authorize/digitally sign all requests in that portion of the workflow, even if you are the original requestor of the form.

I get an error that reads “5. Create Approval_Request__c - Issue with the requestee data. Please contact support.” How can I proceed?

This error indicates that the requestee username is not a primary account. If the account was recently converted to primary, you may need to wait up to 48 hours for the permissions to matriculate into the Federated Authorization Community.

Sponsored accounts generally will not have access to privileged data through the Federated Authorization process. If you believe that the requested account is a service account that is entitled to data protected by the Federated Authorization process, please enter your own username as the requestee. In the Request Details and Justification section, list the name of the sponsored account and the owner of the account. Include any additional information that will be important to the approvers.

What tasks can a Responsibility Center Administrator (RC Admin) perform?

Responsibility Center Administrators can perform the following tasks:

• Add additional email addresses (called email aliases) to individual accounts and groups 
• Create and modify Exchange resources (used to schedule rooms, equipment, and services) 
• Restrict who can send email to a group 
• Require authentication to be able to send email to a group 
• Convert groups between “mail-enabled” and “not mail-enabled” 
• Show or hide groups within the Global Address List 
• Grant “full access” or “send-as” rights to Resource Account mailboxes 
• Set a customized out-of-office message for a user in your responsibility center who is no longer with the University

Where can I learn additional information about RC Admins?

You can learn more here.

Who are the Financial Data Stewards?

• Peter L. DeNardis (pld7@pitt.edu)

Where can I find the list of Approvers for my Request?

• The Financial Data Approvers list is here.
• The Responsibility Center Administrators (RC Admin) list is here.
• The Security Contacts list is here.
• The Financial Data Stewards list is here.
• The Employee Mart Responsibility Center Authorized Approvers (RC HR Approvers) is here>.

How do I find a username?

To find usernames:

• Contact your RC Administrator or your department's IT Contact.
• Use Find Pitt to look up the email address of the user. Unless the person is using an alias, the username will appear before the @ symbol (for example jdoe if the email address is jdoe@pitt.edu). If the user is using an alias, it will be different from the username—aliases will be greater than eight characters or it will contain a period (.), dash (-) or underscore (_) and be greater than 4 characters.  

Note: Requests to clone user access must include the username of the requestee.

If my request is not approved at any stage of the approval process, will I be contacted?

Yes, you will receive an email with information about why the request was not approved.

What steps can I take if I wish to resolve a request that was not approved?

You can submit a new request making sure that you address the specific reason(s) for its rejection.

Are there steps I can take if I need to make specific Federated Authorization access requests to specific departments, rather than an entire school?

Yes. When you submit your request, list any relevant details or specifications, including department or other row-level access.

May I submit a request to clone or duplicate the access of a user who has restricted roles or permissions?

All restricted roles and permissions must be individually selected and justified to ensure proper routing through the Data Stewards. For PeopleSoft, to lookup the roles of an existing user, follow the instructions here: http://pi.tt/SISUserRole.

Are there steps I need to take if I need access to restricted data that is not part of my Responsibility Center (RC)?

Yes, use the following guidelines:

1. Notify the RC Admin for your location. They should contact the appropriate RC approver in the area where the data resides.
2. If you need access to restricted data, Data Stewards approval is part of the request workflow.

Employee Mart

• Using Tableau for Employee Mart Data

Federated Authorization

• Process for Designating Federated Authorization Security Contacts

PeopleSoft

• Definitions of PeopleSoft Roles
• PeopleSoft Security Student Groups
• PeopleSoft Service Indicator Codes
• Videos for Training by PeopleSoft Role

RC Admins

• Directory Services: Using the Accounts Administration Service to Create and Manage Accounts
• Directory Services: Group Account Functions
• Directory Services: How to Enable Group Delegation By Responsibility Center

• Computer Data Administration 10-02-04
• Computer Access and Use 10-02-05
• University Administrative Computer Data Security and Privacy 10-02-06
• Use and Management of Social Security Numbers and University Primary ID Numbers 10-02-08
• University Network 10-02-13
• Access to and Release of Education Records 09-08-01

The following table provides a brief history of changes to the Federated Authorization Community: