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 10 Next »



Alin Hunter, Snezana Popovic, UW-IT – The customers of the groups described in this design template represent the owners of Legacy HR/P Archive reports. also possibly for email notices about the reports.

Application Use

BI Portal – The groups will be used for controlling access to the Legacy HR/P Archive reports hosted in the BI Portal (
TBD. Email – The groups will be used for emailing notices about the Legacy HR/P Archive reports using UW Mailman or Marketo.

Membership (Business Definition)

The business definition of the group memberships is individuals with the assignable security roles in Workday.

For example, someone with the "Academic_Partner" role will be a member of the related group.



Business ProcessWorkday security role management
System of RecordWorkday
Subject AreaMaster Data
Business DomainMaster Data – Services & Resources – HR/P – Access permissions and restrictions
TypeGroup (security role, security group)
Home Groupuw_isc
Group IDs
Workday Security Role IDGroup ID
HR_Auditor (Workday Security Group)uw_isc_security-roles_hr-auditor 
Payroll_Auditor (Workday Security Group)uw_isc_security-roles_payroll-auditor
Display Name

TBD. Display name will be the Workday Security ID... unless Workday has a user-friendly display name for each Workday security role, and it is available in HRPWS.

Lifecycle Policy (Creation)

Groups will be created only for approved uses related to Legacy HR/P Archive reports.

Lifecycle Policy (Deletion)

Groups will be deleted when custodians request and plan for their deletion.

Membership (Direct)

Direct membership of each group include the UW NetIDs of individuals assigned to the specific Workday security role.

Membership (Exceptions)

No exceptions for additions or deletions. Memberships will be provisioned based on data mastered in Workday and provided through HRPWS.

Membership (Grace Period)


Membership (Opt-in)N/A
Membership (Opt-out)N/A
Contact Person

TBD. A contact appropriate for Workday security role support, e.g. "ischelp".


TBD. Define descriptions that help potential customers understand fit for purpose and use, including lifecycle policy, membership policy, data quality standards, appropriate use guidelines, access control policy, ownership, and contact information. Some business processes master data that can be used for descriptions.

More InformationN/A 
Application Settings (Exchange)

Inactive; change to settings will require custodian approval.

Application Settings (Google)

Inactive; change to settings will require custodian approval.

Data Custodian

Nancy Jagger, Rachel Gatlin, Margaret Stuart, Cindy Gregovich



Access Control PolicyTBD. Decide and document the access control policy including membership viewer control, sender control, appropriate use guidelines, terms and conditions of use, etc.
Membership Viewer ControlTBD. Define the membership viewer control, including exceptions to the access control policy.
Sender ControlN/A
Data Source


Membership (Technical)

TBD. Define the technical definition of the memberships in terms used by the data source and its data elements, as well as any additional filtering.

ProvisioningTBD. Define a provisioning model for data integration and reconciliation that ensures the groups are created in accordance with their lifecycle policy and managed in accordance with their data quality standards.
De-ProvisioningTBD. Define a de-provisioning model that ensures the groups are deleted in accordance with their lifecycle policy.
MonitoringTBD. Define a monitoring solution that helps identify incidents and problems, particularly those that impact availability and reliability.
Data Quality Standards

TBD. Define data quality standards under normal operations, including data validation rules, timeliness of updates, defined error rates, integrity monitoring, and reliability. The standards will depend on the business process, system of record, data source, provisioning and de-provisioning models, monitoring, and operations.

Internal DocumentationTBD. Define what internal documentation will be developed and where it will be maintained.
Customer DocumentationTBD. 
Communication PlanTBD. Alin and Snezana will coordinate communications with BI Portal report users and other stakeholders.
Request FulfillmentTBD. Define how requests will be fulfilled. For example, standard requests for information, access to memberships, membership exceptions, email settings, design changes, etc.
Incident ManagementTBD. Define how incidents will be handled.
  • No labels