Below are the A&M System Member support contacts who are authorized to create escalation tickets with ID.me on behalf of pre-hires and former employees. These support contacts can also assist IT support staff with Workday data issues. Note to employees: Please do not contact these individuals directly. If you need help with ID.me, please see […]<\/p>\n","protected":false},"author":38595,"featured_media":0,"parent":2154,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-2448","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/Contacts\/SsoIDMeMemberContactsRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2448","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/38595"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2448"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2448\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2448"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":2154,"date":"2025-11-06T16:28:50","date_gmt":"2025-11-06T22:28:50","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=2154"},"modified":"2026-07-13T11:25:10","modified_gmt":"2026-07-13T16:25:10","slug":"id-me-administration","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/id-me-administration\/","title":{"rendered":"ID.me Administration"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":38474,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-page-builder.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"content-sidebar","footnotes":""},"class_list":["post-2154","page","type-page","status-publish","entry"],"acf":{"page_options":"","custom_page_title":"","banner":{"":null,"banner_options":[],"banner_content":"","background_image":null,"image_overlay_type":"","icon_position":"left","image_overlay_source":null,"svg_source":"","banner_html":"","call_to_action_button":null},"content":[{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"Starting in 2026, ID.me will be replacing SSO's UIN Login for new employees, retirees, and former employees of your university or agency. The exact date of its implementation at your institution will be determined by your HR office.\r\n\r\nAdministration of ID.me is primarily about guiding new employees, retirees, former employees, and certain dependents to the help they need. This guide helps administrators do that.\r\n\r\n "}},{"acf_fc_layout":"tab_layout","tab_options":"","css_class":"","tabs_row":[{"tab_label":"Adoption Guide","tab_content":"
Introduction<\/h2>\r\nThis guide covers\u00a0key\u00a0concepts and\u00a0recommended\u00a0processes for business administrators\u00a0who support employees that access\u00a0A&M System SSO using\u00a0ID.me.\r\nSingle Sign On<\/h2>\r\nThe Texas A&M University System Single Sign On (SSO) is a one-stop-shop that allows individuals from across the A&M System to login and use services, products and tools specifically for those affiliated with the A&M System or one of its members. Individuals who use SSO include:\r\n\r\n \t- Current employees, including student workers<\/li>\r\n \t
- Future employees (aka pre-employees)<\/li>\r\n \t
- Former employees, including retirees<\/li>\r\n \t
- Students<\/li>\r\n \t
- Contractors who are\u00a0a Contingent Worker in Workday<\/li>\r\n<\/ul>\r\n
SSO UIN Logins<\/h2>\r\nMost A&M System members only allow active employees to log into SSO with their member credentials (e.g., Texas A&M University NetID, Texas A&M Corpus Christi IslandID). This is a standard, cybersecurity best practice that unfortunately makes it difficult for non-active employees (e.g. pre-employees, terminations, retirees) to access A&M System SSO and tools like Workday.\r\n\r\nTo grant SSO access to non-active employees, business administrators within human resources, benefits administration, and other departments, can create A&M System SSO login credentials by using the employee\u2019s UIN.\r\n\r\nHowever, in response to evolving cybercriminal tactics, the decision was made in 2024 that UIN login credentials would be phased out. ID.me was selected to replace UIN login credentials to better protect the data and privacy of individuals and the A&M System.\r\n\r\nWhere you would typically use SSO to grant access to pre-employees and retirees, you will now use ID.me. This change improves security and simplifies processes for business administrators.\r\nAbout ID.me<\/h2>\r\nID.me is a 3rd-party user identity authentication platform with a long history of protecting customer data. Their customers range from consumer companies and healthcare organizations to over 20 federal agencies and 45 state government agencies, including the federal Social Security Administration and Internal Revenue Service.\r\nImportant Information Before You Begin<\/h2>\r\nID.me is the official A&M System SSO login for pre-employees and former employees, including retirees. Pre-employees and former employees log into SSO to use applications, like Workday and Insurance Billing, to access employment and benefit information.\r\n\r\nAs the business administrator responsible for managing pre-employees and former employees, you play a crucial role in their onboarding and offboarding process. Therefore, it\u2019s important that you:\r\n\r\n \t- Create or discover the employee\u2019s UIN.<\/li>\r\n \t
- Tell the employee about SSO and ID.me and explain what they are used for.<\/li>\r\n \t
- Ask the employee to create or use their existing ID.me account to log into SSO.<\/li>\r\n \t
- Emphasize to the employee that the information they enter in ID.me must exactly match the information provided to the A&M System.<\/li>\r\n<\/ul>\r\nFor this document, employee specifically refers to those employees who can use ID.me to log into SSO (e.g. pre-employees, former employees, retirees and dependents).\r\n
New Employees and ID.me<\/h3>\r\nOnce your institution adopts ID.me, SSO will no longer send new employees a UIN Login One-time Password (OTP) email.\r\n\r\nIf one of your new employees must use a UIN Login to access SSO, you will need to use SSO's Central Admin role to reset their password. This will send the OTP email to the employee's email address on file.\r\nActive Employees and ID.me<\/h3>\r\nID.me is not<\/strong> for active employees. Once an employee becomes active, they must use their member login credentials<\/strong> to access SSO. Active employees will get an error message if they try to login to SSO with ID.me.\r\n\r\nID.me login is only for:\r\n\r\n \t- Pre-employees<\/strong> who need SSO access before their first day<\/li>\r\n \t
- Former employees<\/strong>, including retirees<\/li>\r\n \t
- Benefit-eligible dependents<\/strong> such as surviving spouses, military dependents, and others<\/li>\r\n<\/ul>\r\nIf your pre-employee does not need to access SSO before their first day, they do not need to create or update an ID.me account. Former employees and benefits eligible dependents will always need to create or update an ID.me account.\r\n
UIN Assignment<\/h2>\r\n\r\n \t- All employees need a UIN.<\/li>\r\n \t
- Before you create a new UIN, always search UIN Manager first to discover if the pre-employee has an existing UIN.<\/li>\r\n \t
- Most pre-employees need to have a UIN created for them.<\/li>\r\n \t
- However, some pre-employees may have an existing UIN.<\/li>\r\n \t
- ID.me will not work if the employee\u2019s UIN Manager record does not include:\r\n
\r\n \t- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Workday Worker Setup<\/h2>\r\n\r\n \t- Once an employee\u2019s UIN is assigned to their Workday record:\r\n
\r\n \t- The Worker record becomes the system of record<\/li>\r\n \t
- You will only use Workday to update an employee\u2019s name, SSN, Date of Birth, and gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Changes automatically flow to UIN Manager\r\n
\r\n \t- Given that there are no UIN\/SSN\/EmployeeID conflicts<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Data Matching Rules<\/h2>\r\nThe following information must be the same in both ID.me, UIN Manager, and Workday:\r\n\r\n \t- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\nIf one or more of these values do not match, the employee may experience issues. The A&M System Office of IT support team will work with the employee, and potentially your HR team, to ensure accuracy and consistency across ID.me, UIN Manager, and Workday.\r\n
Employee Responsibilities and Account Setup<\/h2>\r\n\r\n \t- The employees\u2019 relationship with ID.me is separate and distinct from their relationship with the A&M System.<\/li>\r\n \t
- The employee is responsible for their ID.me account.<\/li>\r\n \t
- The employee is responsible for managing their ID.me account before, during, and after their time as an employee with the A&M System.<\/li>\r\n \t
- If the employee has an existing ID.me account, they should use their existing ID.me account.<\/li>\r\n \t
- The employee is responsible for creating their ID.me account.<\/li>\r\n \t
- The employee must meet the requirements for a \u201cverified identity\u201d ID.me account, regardless of whether it is a new or existing ID.me account.\r\n
\r\n \t- This includes visual verification of a valid picture ID and SSN<\/li>\r\n \t
- This also includes enabling multi-factor authentication<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee should create\/update their ID.me account using the same exact information that they provided to the A&M System.<\/li>\r\n \t
- When the employee uses ID.me to log into SSO for the first time, they must agree to release their attributes or else they will not be able to log into SSO.<\/li>\r\n<\/ul>"},{"tab_label":"Business Processes","tab_content":"
Introduction<\/h2>\r\nBelow are the recommended ID.me business processes for pre-employees and former employees. Your member organization processes can be different than those outlined below. However, we highly encourage you to follow the recommended processes to minimize potential issues.\r\n\r\nIt\u2019s important to note that automatic overnight data syncs impact certain steps in the recommended ID.me business process.\r\nID.me and Pre-Employees<\/h2>\r\nPre-employees can access A&M System SSO up to 45 days prior to their employment start date. This allows pre-employees to complete important onboarding tasks in applications like Workday before their first day.\r\n\r\nWhenever possible, pre-employees who need to log into A&M System SSO before their first day of work should use ID.me.\r\n\r\nFollow the steps below to grant your pre-employees SSO access:\r\n\r\n \t- Collect the following information for your pre-employee<\/li>\r\n<\/ol>\r\n
\r\n \t- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\nConfirm that this information is accurate\r\n
\r\n \t- Log into UIN Manager and search for the pre-employee\u2019s existing UIN<\/li>\r\n<\/ol>\r\n
\r\n \t- If the pre-employee does not have a UIN:\r\n
\r\n \t- Create a new UIN for the pre-employee using the collected information from above.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
\r\n \t- If the pre-employee has an existing UIN:\r\n
\r\n \t- Review the information in UIN Manager and make any necessary updates so that it matches the information provided by the pre-employee.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
\r\n \t- Next, create the pre-employee\u2019s record in Workday with as much of the following information as you can:<\/li>\r\n<\/ol>\r\n
\r\n \t- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n
\r\n \t- The next business day<\/strong>, confirm that the pre-employee\u2019s record was successfully created in SSO by using the SSO Central or Department Administrator role.*\r\n
\r\n \t- Currently, this is an overnight process. This information will not show up in SSO if you check the same day you create the pre-employee's record in Workday.<\/li>\r\n \t
- Once the pre-employee record is confirmed in SSO, contact the pre-employee and tell them to log into SSO with ID.me. Feel free to use the email templates provided.<\/li>\r\n \t
- Please note<\/strong>: Do not ask the employee to log into SSO before completing the steps above or the pre-employee will experience issues<\/li>\r\n \t
- When you contact the pre-employee, make sure you explain:\r\n
\r\n \t- They have exactly 1 ID.me account. They should create a new ID.me account or use their existing ID.me account.<\/li>\r\n \t
- Their ID.me account is theirs, independent of their employment with the A&M System.<\/li>\r\n \t
- Their ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Their ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n \t
- Two-factor authentication is required.<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ol>\r\n
\r\n \t- Provide them with these instructions to log into SSO with ID.me\r\n
\r\n \t- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Select the ID.me icon.<\/li>\r\n \t
- Create\/update your ID.me account<\/li>\r\n \t
- Check that the information in ID.me exactly matches what you provided the A&M system<\/li>\r\n \t
- Complete all requirements for a \u201cverified identity\u201d account including two-factor authentication<\/li>\r\n \t
- Select \u201cagree\u201d when asked to release your ID.me attributes<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ol>\r\nNOTE: If a new employee must use a UIN Login to access SSO, an SSO Central Admin will need to reset their password in order for the employee to receive their one-time password from SSO.\r\n
ID.me and Former Employees<\/h2>\r\nMost institutions deactivate an employee\u2019s login credentials upon termination, including retirement. Therefore, after an active employee or working retiree transitions to Terminated or Retired status, they should use ID.me to log into SSO.\r\n\r\nThe same considerations for pre-employees apply to former employees, including the data matching rules for ID.me and UIN Manager.\r\n\r\nFollow the steps below when terminating an employee, including retirement.\r\n\r\n \t- \r\n
\r\n \t- \r\n
\r\n \t- Verify the following employee information in Workday and make updates if needed:\r\n
\r\n \t- Full legal name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The next business day<\/strong>, confirm that the employee\u2019s record was successfully created in SSO by using the SSO Central or Department Administrator role.*\r\n
\r\n \t- Currently, this is an overnight process. This information will not show up in SSO if you check the same day you made updates in Workday.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Once the employee record is confirmed in SSO, contact the employee and tell them they will now use ID.me to log into SSO. Feel free to use the email templates provided.\r\n
\r\n \t- Please note: Do not ask the employee to log into SSO before completing steps 1 and 2 or the employee will experience issues<\/li>\r\n \t
- When you contact the employee, make sure you explain:\r\n
\r\n \t- They have exactly 1 ID.me account. They should create a new ID.me account or use their existing ID.me account.<\/li>\r\n \t
- Their ID.me account is theirs, independent of their employment with the A&M System.<\/li>\r\n \t
- Their ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Their ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n \t
- Two-factor authentication is required.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Provide them with these instructions to log into SSO with ID.me\r\n
\r\n \t- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Select the ID.me icon.<\/li>\r\n \t
- Create\/update your ID.me account<\/li>\r\n \t
- Check that the information in ID.me exactly matches what you provided the A&M system<\/li>\r\n \t
- Complete all requirements for a \u201cverified identity\u201d account including two-factor authentication<\/li>\r\n \t
- Select \u201cagree\u201d when asked to release your ID.me attributes<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
ID.me and Active Employees<\/h2>\r\nActive employees, contractors, student workers, graduate students, and working retirees should use their institutional login credentials<\/a> to access A&M System SSO. They will get an error message if they try to login using ID.me.\r\nID.me and Affiliate Users<\/h2>\r\nAffiliates of A&M System members can use ID.me to log in to SSO only if they have a Workday Contingent Worker account<\/strong>.\r\n\r\nAll other affiliates should use the university\/agency credential (alternate login)<\/a> provided by the institution rather than ID.me. This includes contractors, students, and other individuals who work with the A&M System but do not have a Workday account.\r\nHelp With ID.me<\/h2>\r\nIf an employee has issues with ID.me, follow these instructions:\r\n\r\n \t- \r\n
\r\n \t- If they ran into an issue when creating a new ID.me account or logging into an existing ID.me account.\r\n
\r\n \t- Ask the employee to review the ID.me help page<\/a>.<\/li>\r\n \t
- If this doesn't resolve their issue:\r\n
\r\n \t- Gather the following information from them:\r\n
\r\n \t- Name<\/li>\r\n \t
- UIN (if known, for later use if needed)<\/li>\r\n \t
- Email address<\/li>\r\n \t
- Phone number<\/li>\r\n \t
- A brief description of the problem<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Write an email to the ID.me Escalation support team including this information.<\/li>\r\n \t
- Have your institution's ID.me Support Contact<\/a> send the message to ID.me <\/strong>to open a priority ticket with ID.me on the employee's behalf.\r\n
\r\n \t- NOTE: If you are a member administrator and need the ID.me Escalation team's email address, contact support@tamus.edu<\/strong>.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Advise the employee that ID.me will proactively contact them - typically within one (1) hour - to resolve the issue.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee successfully created\/logged into their ID.me account but cannot log into A&M SSO using ID.me.\r\n
\r\n \t- Tell the employee to:\r\n
\r\n \t- Email support@tamus.edu<\/strong><\/li>\r\n \t
- Include ID.me in the subject line<\/li>\r\n \t
- Include their legal name, email and UIN if known<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The A&M System IT Shared Services support team will advise on next steps.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee does not have an SSN, ITIN, international passport, is under the age of 18, or is acting with Power of Attorney.\r\n
\r\n \t- Use UIN login for these edge cases.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Resources<\/h2>\r\nAdministrator ID.me FAQ Document<\/a>\r\n\r\nEmployee ID.me Support Material<\/a>"},{"tab_label":"Email Templates","tab_content":"Introduction<\/h2>\r\nAdministrators are responsible for directing new employees, retirees, and former employees to ID.me. These email templates provide a starting point for communications with your employees.\r\nPre-Employee Template<\/h2>\r\nCongratulations on your new role with [organization]. During your time with [organization] you\u2019ll use The Texas A&M University System Single Sign On (SSO) as a one-stop-shop to login and access services, applications, products and tools.\r\n\r\nAs a pre-employee, you will use ID.me to log into SSO before your start date. A few important things to know before you get started:\r\n\r\n \t- You have exactly 1 ID.me account. Use your existing ID.me account if you already have one.<\/li>\r\n \t
- Your ID.me account is yours, independent of your employment with the A&M System.<\/li>\r\n \t
- Your ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Your ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n<\/ul>\r\nPlease log into SSO using the instructions below.\r\n
\r\n \t- Visit the SSO login pageand select the ID.me icon.<\/li>\r\n \t
- Create a new ID.me account or log into your existing ID.me account.<\/li>\r\n \t
- Make sure the following fields in your ID.me account exactly match the information you have already provided us.\r\n
\r\n \t- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Complete all necessary requirements to obtain a \u201cverified identity\u201d including enabling two-factor authentication.<\/li>\r\n \t
- When asked if you want to release your attributes, select \u201cagree\u201d.\r\n
\r\n \t- If you do not select \u201cagree\u201d you will not be able to log into SSO.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- You should be automatically redirected the A&M System SSO menu page.<\/li>\r\n \t
- Reply to this email and let me know that you have successfully logged into A&M System SSO.<\/li>\r\n<\/ul>\r\nIf you experience issues during this process, follow the recommendations below.\r\n
\r\n \t- If you have problems with creating, logging into, or updating your ID.me account, review the ID.me troubleshooting guide or contact ID.me support.<\/li>\r\n \t
- If you are able to create\/log into\/update your ID.me account, but are unable to access A&M System SSO, please email support@tamus.edu and include \u201cID.me\u201d in the subject line and your full legal name in the email body.<\/li>\r\n<\/ul>\r\nThank you,\r\n\r\n[Signature]\r\n
Former Employee Template<\/h2>\r\nAs a former employee of [organization], you will no longer log into The Texas A&M University System Single Sign On (SSO) using your [organization] credentials. Instead, you will log into SSO using ID.me.\r\n\r\nA few important things to know before you get started:\r\n\r\n \t- You have exactly 1 ID.me account. Use your existing ID.me account if you already have one.<\/li>\r\n \t
- Your ID.me account is yours, independent of your employment with the A&M System.<\/li>\r\n \t
- Your ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Your ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n<\/ul>\r\nPlease log into SSO using the instructions below.\r\n
\r\n \t- Visit the SSO login pageand select the ID.me icon.<\/li>\r\n \t
- Create a new ID.me account or log into your existing ID.me account.<\/li>\r\n \t
- Make sure the following fields in your ID.me account exactly match the information you have already provided us.\r\n
\r\n \t- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Complete all necessary requirements to obtain a \u201cverified identity\u201d including enabling two-factor authentication.<\/li>\r\n \t
- When asked if you want to release your attributes, select \u201cagree\u201d.\r\n
\r\n \t- If you do not select \u201cagree\u201d you will not be able to log into SSO.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- You should be automatically redirected the A&M System SSO menu page.<\/li>\r\n<\/ul>\r\nIf you experience issues during this process, follow the recommendations below.\r\n
\r\n \t- If you experience issues creating or updating your ID.me account, review the ID.me troubleshooting guide or contact ID.me support.<\/li>\r\n \t
- If you were able to create\/update your ID.me account, but are unable to log into A&M System SSO, please email support@tamus.edu and include \u201cID.me\u201d in the subject line and include your full legal name and UIN in the email body.<\/li>\r\n<\/ul>\r\nThank you,\r\n\r\n[Signature]"}]}]},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/38474"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2154"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154\/revisions"}],"predecessor-version":[{"id":2465,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154\/revisions\/2465"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2154"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":2063,"date":"2025-08-14T08:28:01","date_gmt":"2025-08-14T13:28:01","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=2063"},"modified":"2025-10-16T14:07:42","modified_gmt":"2025-10-16T19:07:42","slug":"identity-providers","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/identity-providers\/","title":{"rendered":"Identity Providers"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":35,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-2063","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/IdentityProviders\/IdentityProvidersRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2063"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2063\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":2045,"date":"2025-06-10T11:32:39","date_gmt":"2025-06-10T16:32:39","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=2045"},"modified":"2026-06-25T19:27:17","modified_gmt":"2026-06-26T00:27:17","slug":"alerts","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/alerts\/","title":{"rendered":"SSO Alerts"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-2045","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/HomepageMessages\/HomepageMessagesRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2045","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2045"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2045\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1923,"date":"2025-05-29T08:46:22","date_gmt":"2025-05-29T13:46:22","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1923"},"modified":"2026-06-29T14:42:51","modified_gmt":"2026-06-29T19:42:51","slug":"id-me","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/id-me\/","title":{"rendered":"Using ID.me"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":35,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-page-builder.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1923","page","type-page","status-publish","entry"],"acf":{"page_options":"","custom_page_title":"","banner":{"":null,"banner_options":[],"banner_content":"","background_image":null,"image_overlay_type":"","icon_position":"left","image_overlay_source":null,"svg_source":"","banner_html":"","call_to_action_button":null},"content":[{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":"","column_content":"ID.me is an identity verification service trusted by many federal and state agencies, including the Social Security Administration, Medicare, the IRS, and The Texas A&M University System. To learn more, watch a short video about ID.me<\/a>.\r\n\r\nSee ID.me Frequently Asked Questions<\/a> for more information.\r\n\r\nHow you use ID.me depends on your relationship with the A&M System.\r\n
New Hires, Retirees, and Former Employees<\/h2>\r\n\r\n\r\nStarting November 1st, 2026, pre-hire personnel, retirees, and former employees will no longer use SSO's UIN Login. Instead, these users will be required to use ID.me for authentication with SSO.\r\n\r\nAnyone who already has a valid A&M System credential can use that login; e.g., new student workers and certain retirees.\r\n\r\n"}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p","card","css"],"css_class":"id-me-hi-info-card ","card_link":"","column_content":"New to ID.me?<\/h3>\r\nYou must have a verified account to use ID.me. First, review ID.me's list of required documents<\/a>. Then, see SSO's Creating an ID.me account page<\/a> to get started. If you need help, visit the Getting Help page<\/a>."}},{"acf_fc_layout":"tab_layout","tab_options":"","css_class":"","tabs_row":[{"tab_label":"Logging in with ID.me","tab_content":"Select the ID.me logo from the Single Sign On (SSO) login page.\r\n![\"Screen](\"https:\/\/it.tamus.edu\/sso\/wp-content\/uploads\/sites\/4\/2025\/05\/IDme_logo-274x300.png\")
<\/a><\/figure>\r\n\r\n\r\nThe following screen will ask for your Universal Identification Number (UIN) to verify your eligibility to use the ID.me login:\r\n![\"\"](\"https:\/\/it.tamus.edu\/sso\/wp-content\/uploads\/sites\/4\/2026\/06\/SSO-ID-me-verification-1.png\")
<\/a><\/figure>\r\n\r\n\r\nIf you are eligible to use ID.me, you will be redirected to the ID.me site to log in.\r\n\r\nIf you already have an ID.me account, use your existing username and password to log in.\r\n\r\nOtherwise, create an ID.me account<\/a> and verify your identity with them.\r\n\r\n\r\n\r\nAfter logging into ID.me for the first time, you will authorize A&M System to access your verified identity information. Clicking \u201cDeny\u201d will prevent you from logging in to SSO with your ID.me account.\r\n![\"Screen](\"https:\/\/it.tamus.edu\/sso\/wp-content\/uploads\/sites\/4\/2025\/05\/IDme_homescreen-167x300.png\")
<\/a><\/figure>"},{"tab_label":"Creating Your Account","tab_content":"<\/a>Creating your ID.me account is easy. You can do it entirely on your own, without assistance from your A&M System HR or benefits representative. View ID.me's step-by-step instructions<\/a>\u00a0or view a step-by-step video<\/a>.\r\n\r\nNOTE: Your ID.me account belongs to you and it is independent of your relationship with the A&M System. You can use it with other entities such as the Social Security Administration, Medicare, and the Internal Revenue Service.\r\n\r\nWhat you need to create your ID.me account:\r\n\r\n \t- A smartphone, tablet, or computer with a camera<\/span><\/li>\r\n \t
- Photo ID (U.S. driver\u2019s license or state ID, U.S. passport, or U.S. passport card)<\/li>\r\n \t
- An official government identification number:\r\n
\r\n \t- Social Security Number<\/a> (SSN)<\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a> (ITIN)<\/li>\r\n \t
- International Passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n\r\n\r\n\r\nPlease note that the information you provide ID.me must match your legal name, social security number, and birth date in Workday.\u00a0<\/strong>Contact your Human Resources department if a Workday change is needed.\r\n\r\n\r\n\r\nTo create your account:\r\n
\r\n \t- Click the ID.me<\/strong> link in SSO<\/li>\r\n \t
- Verify your UIN<\/li>\r\n \t
- Follow ID.me's instructions<\/a> to create your account using:\r\n
\r\n \t- Social Security Number<\/a>\u00a0(SSN)<\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a>\u00a0(ITIN)<\/li>\r\n \t
- International passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Set up multi-factor authentication on your ID.me account<\/a><\/li>\r\n<\/ul>\r\nRefer to our Getting Help<\/a> page if you need help creating your account."},{"tab_label":"Getting Help","tab_content":"An excellent resource is\u00a0the Social Security Administration's video about the ID.me account setup process<\/a>.\r\n\r\nFor help with with ID.me, please consult the following links.\r\n
\r\n \t- ID.me frequently asked questions<\/a><\/li>\r\n \t
- ID.me required documents<\/a><\/li>\r\n \t
- ID.me account creation step-by-step guide<\/a><\/li>\r\n \t
- ID.me identity verification guides using:\r\n
\r\n \t- SSN<\/a><\/li>\r\n \t
- ITIN<\/a><\/li>\r\n \t
- Non-US Passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Using a video call with ID.me<\/a><\/li>\r\n \t
- Troubleshooting ID.me issues<\/a><\/li>\r\n<\/ul>\r\nIf you need more assistance, contact us!<\/strong>\r\n
\r\n \t- ID.me issues<\/strong>: Contact TAMU Help Desk Central\r\n
\r\n \t- 979-845-8300 (available 8:00 AM to Midnight)<\/li>\r\n \t
- helpdesk@tamu.edu<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Single Sign On issues<\/strong>: Contact A&M System Support\r\n
\r\n \t- support@tamus.edu<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>"}]},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"
Current Employees<\/h2>\r\nActive employees of the A&M System should use their university\/agency credentials (alternate login)<\/a> rather than ID.me."}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"Affiliate Users<\/h2>\r\nAffiliates of A&M System members can use ID.me to log in to SSO only if they have a Workday Contingent Worker account<\/strong>.\r\n\r\nAll other affiliates should use the university\/agency credential (alternate login)<\/a> provided by the institution rather than ID.me. This includes contractors, students, and other individuals who work with the A&M System but do not have a Workday account."}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"Department and Central Administrators<\/h2>\r\nSSO department and central administrators can help new employees, retirees, and former employees learn to use ID.me effectively.\r\n\r\nLearn more about administering ID.me for Single Sign On<\/a>"}}]},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1923"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1923\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1995,"date":"2025-05-09T10:17:52","date_gmt":"2025-05-09T15:17:52","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1995"},"modified":"2025-10-16T14:07:17","modified_gmt":"2025-10-16T19:07:17","slug":"applications","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/applications\/","title":{"rendered":"Applications"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":50,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1995","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/ApplicationCodes\/ApplicationCodesRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1995"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1995\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1814,"date":"2024-08-02T16:43:29","date_gmt":"2024-08-02T21:43:29","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1814"},"modified":"2024-08-02T16:45:05","modified_gmt":"2024-08-02T21:45:05","slug":"sso-security-teams","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/sso-security-teams\/","title":{"rendered":"SSO Security Teams"},"content":{"rendered":"These are the SSO Security team contacts for A&M System member institutions.<\/p>\n","protected":false},"excerpt":{"rendered":"
These are the SSO Security team contacts for A&M System member institutions.<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":35,"menu_order":999,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1814","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/Contacts\/SsoSecurityTeamContactRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1814"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1814\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1775,"date":"2024-06-03T14:47:36","date_gmt":"2024-06-03T19:47:36","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1775"},"modified":"2025-10-16T13:59:21","modified_gmt":"2025-10-16T18:59:21","slug":"redirects","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/redirects\/","title":{"rendered":"SSO Redirects"},"content":{"rendered":"
\n\n![\"Notification](\"https:\/\/sso.tamus.edu\/Resources\/Images\/ssolock.png\")
<\/p>\n\nThe Single Sign On site – https:\/\/sso.tamus.edu<\/a> – is the ONLY site authorized to collect your SSO UIN and password.<\/strong>\n<\/div>\n<\/div>\n<\/div>\n\nIf you use a campus or agency federated logon, please educate yourself on the sites and systems authorized to collect that username and password.\n<\/div>\n\nGo to https:\/\/sso.tamus.edu<\/a> now<\/strong>.\n<\/div>\n","protected":false},"excerpt":{"rendered":"The Single Sign On site – https:\/\/sso.tamus.edu – is the ONLY site authorized to collect your SSO UIN and password. If you use a campus or agency federated logon, please educate yourself on the sites and systems authorized to collect that username and password. Go to https:\/\/sso.tamus.edu now.<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":35,"menu_order":1000,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1775","page","type-page","status-publish","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1775"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1775\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1239,"date":"2021-04-13T17:15:23","date_gmt":"2021-04-13T22:15:23","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1239"},"modified":"2025-10-16T14:02:26","modified_gmt":"2025-10-16T19:02:26","slug":"application-role-reviewer-responsibilities-new","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/application-role-reviewer-responsibilities-new\/","title":{"rendered":"Application Role Reviewer Responsibilities"},"content":{"rendered":"
Member institutions must regularly review which of their employees have what roles (privileges) in the various SSO applications, and update those roles to reflect departures or transfers.\u00a0 For example, if an employee had roles in File Depot but is no longer employed by a particular institution, then those roles should be removed.\u00a0 Similarly, if that employee is still employed but has moved to a different position that no longer requires access to FileDepot, then those roles should also be removed.<\/p>\n
If you are an Application Role Reviewer you have one or both of the following\u00a0scopes\u00a0<\/em>of review, depending on what has been assigned to you.<\/p>\n\n- Department level: Responsible for one or more\u00a0Adlocs<\/em>, with a semi-annual review period (January 1st and July 1st).<\/li>\n
- Member level:\u00a0 Responsible for one or more\u00a0system members,\u00a0<\/em>with a more frequent quarterly review period (January, April, July and October 1st).<\/li>\n<\/ol>\n
On the 1st of the month of your quarterly or semi-annually review period, the SSO system will generate a reminder email to\u00a0the system members’ Application Security Officer(s)<\/a> and Application Role Reviewer(s)<\/a> reminding them to perform this required security review.\u00a0 This review should be finished by the 10th of the month.\u00a0 On the 11th day of the review period, the System-wide SSO Member-level Role Verification Report will be sent to the Application Owner and the System Chief Information Security Officer(s).<\/p>\nConsequences for Missing or Incomplete Reviews<\/strong><\/p>\nMissing reviews may lead to the loss of administrative role authorizations for the member institution’s \u00a0ASOs, ARRs, and\/or administrative role holders at the institution.<\/p>\n
Additional Documentation\u00a0 (needs removed or updated)<\/strong><\/p>\nFor a visual description of the role review process, view the Security Review Process flowchart<\/a>.<\/p>\n
- \r\n \t
- Current employees, including student workers<\/li>\r\n \t
- Future employees (aka pre-employees)<\/li>\r\n \t
- Former employees, including retirees<\/li>\r\n \t
- Students<\/li>\r\n \t
- Contractors who are\u00a0a Contingent Worker in Workday<\/li>\r\n<\/ul>\r\n
SSO UIN Logins<\/h2>\r\nMost A&M System members only allow active employees to log into SSO with their member credentials (e.g., Texas A&M University NetID, Texas A&M Corpus Christi IslandID). This is a standard, cybersecurity best practice that unfortunately makes it difficult for non-active employees (e.g. pre-employees, terminations, retirees) to access A&M System SSO and tools like Workday.\r\n\r\nTo grant SSO access to non-active employees, business administrators within human resources, benefits administration, and other departments, can create A&M System SSO login credentials by using the employee\u2019s UIN.\r\n\r\nHowever, in response to evolving cybercriminal tactics, the decision was made in 2024 that UIN login credentials would be phased out. ID.me was selected to replace UIN login credentials to better protect the data and privacy of individuals and the A&M System.\r\n\r\nWhere you would typically use SSO to grant access to pre-employees and retirees, you will now use ID.me. This change improves security and simplifies processes for business administrators.\r\n
About ID.me<\/h2>\r\nID.me is a 3rd-party user identity authentication platform with a long history of protecting customer data. Their customers range from consumer companies and healthcare organizations to over 20 federal agencies and 45 state government agencies, including the federal Social Security Administration and Internal Revenue Service.\r\n
Important Information Before You Begin<\/h2>\r\nID.me is the official A&M System SSO login for pre-employees and former employees, including retirees. Pre-employees and former employees log into SSO to use applications, like Workday and Insurance Billing, to access employment and benefit information.\r\n\r\nAs the business administrator responsible for managing pre-employees and former employees, you play a crucial role in their onboarding and offboarding process. Therefore, it\u2019s important that you:\r\n
- \r\n \t
- Create or discover the employee\u2019s UIN.<\/li>\r\n \t
- Tell the employee about SSO and ID.me and explain what they are used for.<\/li>\r\n \t
- Ask the employee to create or use their existing ID.me account to log into SSO.<\/li>\r\n \t
- Emphasize to the employee that the information they enter in ID.me must exactly match the information provided to the A&M System.<\/li>\r\n<\/ul>\r\nFor this document, employee specifically refers to those employees who can use ID.me to log into SSO (e.g. pre-employees, former employees, retirees and dependents).\r\n
New Employees and ID.me<\/h3>\r\nOnce your institution adopts ID.me, SSO will no longer send new employees a UIN Login One-time Password (OTP) email.\r\n\r\nIf one of your new employees must use a UIN Login to access SSO, you will need to use SSO's Central Admin role to reset their password. This will send the OTP email to the employee's email address on file.\r\n
Active Employees and ID.me<\/h3>\r\nID.me is not<\/strong> for active employees. Once an employee becomes active, they must use their member login credentials<\/strong> to access SSO. Active employees will get an error message if they try to login to SSO with ID.me.\r\n\r\nID.me login is only for:\r\n
- \r\n \t
- Pre-employees<\/strong> who need SSO access before their first day<\/li>\r\n \t
- Former employees<\/strong>, including retirees<\/li>\r\n \t
- Benefit-eligible dependents<\/strong> such as surviving spouses, military dependents, and others<\/li>\r\n<\/ul>\r\nIf your pre-employee does not need to access SSO before their first day, they do not need to create or update an ID.me account. Former employees and benefits eligible dependents will always need to create or update an ID.me account.\r\n
UIN Assignment<\/h2>\r\n
- \r\n \t
- All employees need a UIN.<\/li>\r\n \t
- Before you create a new UIN, always search UIN Manager first to discover if the pre-employee has an existing UIN.<\/li>\r\n \t
- Most pre-employees need to have a UIN created for them.<\/li>\r\n \t
- However, some pre-employees may have an existing UIN.<\/li>\r\n \t
- ID.me will not work if the employee\u2019s UIN Manager record does not include:\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Workday Worker Setup<\/h2>\r\n
- \r\n \t
- Once an employee\u2019s UIN is assigned to their Workday record:\r\n
- \r\n \t
- The Worker record becomes the system of record<\/li>\r\n \t
- You will only use Workday to update an employee\u2019s name, SSN, Date of Birth, and gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Changes automatically flow to UIN Manager\r\n
- \r\n \t
- Given that there are no UIN\/SSN\/EmployeeID conflicts<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Data Matching Rules<\/h2>\r\nThe following information must be the same in both ID.me, UIN Manager, and Workday:\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\nIf one or more of these values do not match, the employee may experience issues. The A&M System Office of IT support team will work with the employee, and potentially your HR team, to ensure accuracy and consistency across ID.me, UIN Manager, and Workday.\r\n
Employee Responsibilities and Account Setup<\/h2>\r\n
- \r\n \t
- The employees\u2019 relationship with ID.me is separate and distinct from their relationship with the A&M System.<\/li>\r\n \t
- The employee is responsible for their ID.me account.<\/li>\r\n \t
- The employee is responsible for managing their ID.me account before, during, and after their time as an employee with the A&M System.<\/li>\r\n \t
- If the employee has an existing ID.me account, they should use their existing ID.me account.<\/li>\r\n \t
- The employee is responsible for creating their ID.me account.<\/li>\r\n \t
- The employee must meet the requirements for a \u201cverified identity\u201d ID.me account, regardless of whether it is a new or existing ID.me account.\r\n
- \r\n \t
- This includes visual verification of a valid picture ID and SSN<\/li>\r\n \t
- This also includes enabling multi-factor authentication<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee should create\/update their ID.me account using the same exact information that they provided to the A&M System.<\/li>\r\n \t
- When the employee uses ID.me to log into SSO for the first time, they must agree to release their attributes or else they will not be able to log into SSO.<\/li>\r\n<\/ul>"},{"tab_label":"Business Processes","tab_content":"
Introduction<\/h2>\r\nBelow are the recommended ID.me business processes for pre-employees and former employees. Your member organization processes can be different than those outlined below. However, we highly encourage you to follow the recommended processes to minimize potential issues.\r\n\r\nIt\u2019s important to note that automatic overnight data syncs impact certain steps in the recommended ID.me business process.\r\n
ID.me and Pre-Employees<\/h2>\r\nPre-employees can access A&M System SSO up to 45 days prior to their employment start date. This allows pre-employees to complete important onboarding tasks in applications like Workday before their first day.\r\n\r\nWhenever possible, pre-employees who need to log into A&M System SSO before their first day of work should use ID.me.\r\n\r\nFollow the steps below to grant your pre-employees SSO access:\r\n
- \r\n \t
- Collect the following information for your pre-employee<\/li>\r\n<\/ol>\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- Social Security Number (SSN)<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\nConfirm that this information is accurate\r\n
- \r\n \t
- Log into UIN Manager and search for the pre-employee\u2019s existing UIN<\/li>\r\n<\/ol>\r\n
- \r\n \t
- If the pre-employee does not have a UIN:\r\n
- \r\n \t
- Create a new UIN for the pre-employee using the collected information from above.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- \r\n \t
- If the pre-employee has an existing UIN:\r\n
- \r\n \t
- Review the information in UIN Manager and make any necessary updates so that it matches the information provided by the pre-employee.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- \r\n \t
- Next, create the pre-employee\u2019s record in Workday with as much of the following information as you can:<\/li>\r\n<\/ol>\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n
- \r\n \t
- The next business day<\/strong>, confirm that the pre-employee\u2019s record was successfully created in SSO by using the SSO Central or Department Administrator role.*\r\n
- \r\n \t
- Currently, this is an overnight process. This information will not show up in SSO if you check the same day you create the pre-employee's record in Workday.<\/li>\r\n \t
- Once the pre-employee record is confirmed in SSO, contact the pre-employee and tell them to log into SSO with ID.me. Feel free to use the email templates provided.<\/li>\r\n \t
- Please note<\/strong>: Do not ask the employee to log into SSO before completing the steps above or the pre-employee will experience issues<\/li>\r\n \t
- When you contact the pre-employee, make sure you explain:\r\n
- \r\n \t
- They have exactly 1 ID.me account. They should create a new ID.me account or use their existing ID.me account.<\/li>\r\n \t
- Their ID.me account is theirs, independent of their employment with the A&M System.<\/li>\r\n \t
- Their ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Their ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n \t
- Two-factor authentication is required.<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ol>\r\n
- \r\n \t
- Provide them with these instructions to log into SSO with ID.me\r\n
- \r\n \t
- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Select the ID.me icon.<\/li>\r\n \t
- Create\/update your ID.me account<\/li>\r\n \t
- Check that the information in ID.me exactly matches what you provided the A&M system<\/li>\r\n \t
- Complete all requirements for a \u201cverified identity\u201d account including two-factor authentication<\/li>\r\n \t
- Select \u201cagree\u201d when asked to release your ID.me attributes<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ol>\r\nNOTE: If a new employee must use a UIN Login to access SSO, an SSO Central Admin will need to reset their password in order for the employee to receive their one-time password from SSO.\r\n
ID.me and Former Employees<\/h2>\r\nMost institutions deactivate an employee\u2019s login credentials upon termination, including retirement. Therefore, after an active employee or working retiree transitions to Terminated or Retired status, they should use ID.me to log into SSO.\r\n\r\nThe same considerations for pre-employees apply to former employees, including the data matching rules for ID.me and UIN Manager.\r\n\r\nFollow the steps below when terminating an employee, including retirement.\r\n
- \r\n \t
- \r\n
- \r\n \t
- \r\n
- \r\n \t
- Verify the following employee information in Workday and make updates if needed:\r\n
- \r\n \t
- Full legal name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The next business day<\/strong>, confirm that the employee\u2019s record was successfully created in SSO by using the SSO Central or Department Administrator role.*\r\n
- \r\n \t
- Currently, this is an overnight process. This information will not show up in SSO if you check the same day you made updates in Workday.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Once the employee record is confirmed in SSO, contact the employee and tell them they will now use ID.me to log into SSO. Feel free to use the email templates provided.\r\n
- \r\n \t
- Please note: Do not ask the employee to log into SSO before completing steps 1 and 2 or the employee will experience issues<\/li>\r\n \t
- When you contact the employee, make sure you explain:\r\n
- \r\n \t
- They have exactly 1 ID.me account. They should create a new ID.me account or use their existing ID.me account.<\/li>\r\n \t
- Their ID.me account is theirs, independent of their employment with the A&M System.<\/li>\r\n \t
- Their ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Their ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n \t
- Two-factor authentication is required.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Provide them with these instructions to log into SSO with ID.me\r\n
- \r\n \t
- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Select the ID.me icon.<\/li>\r\n \t
- Create\/update your ID.me account<\/li>\r\n \t
- Check that the information in ID.me exactly matches what you provided the A&M system<\/li>\r\n \t
- Complete all requirements for a \u201cverified identity\u201d account including two-factor authentication<\/li>\r\n \t
- Select \u201cagree\u201d when asked to release your ID.me attributes<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
ID.me and Active Employees<\/h2>\r\nActive employees, contractors, student workers, graduate students, and working retirees should use their institutional login credentials<\/a> to access A&M System SSO. They will get an error message if they try to login using ID.me.\r\n
ID.me and Affiliate Users<\/h2>\r\nAffiliates of A&M System members can use ID.me to log in to SSO only if they have a Workday Contingent Worker account<\/strong>.\r\n\r\nAll other affiliates should use the university\/agency credential (alternate login)<\/a> provided by the institution rather than ID.me. This includes contractors, students, and other individuals who work with the A&M System but do not have a Workday account.\r\n
Help With ID.me<\/h2>\r\nIf an employee has issues with ID.me, follow these instructions:\r\n
- \r\n \t
- \r\n
- \r\n \t
- If they ran into an issue when creating a new ID.me account or logging into an existing ID.me account.\r\n
- \r\n \t
- Ask the employee to review the ID.me help page<\/a>.<\/li>\r\n \t
- If this doesn't resolve their issue:\r\n
- \r\n \t
- Gather the following information from them:\r\n
- \r\n \t
- Name<\/li>\r\n \t
- UIN (if known, for later use if needed)<\/li>\r\n \t
- Email address<\/li>\r\n \t
- Phone number<\/li>\r\n \t
- A brief description of the problem<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Write an email to the ID.me Escalation support team including this information.<\/li>\r\n \t
- Have your institution's ID.me Support Contact<\/a> send the message to ID.me <\/strong>to open a priority ticket with ID.me on the employee's behalf.\r\n
- \r\n \t
- NOTE: If you are a member administrator and need the ID.me Escalation team's email address, contact support@tamus.edu<\/strong>.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Advise the employee that ID.me will proactively contact them - typically within one (1) hour - to resolve the issue.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee successfully created\/logged into their ID.me account but cannot log into A&M SSO using ID.me.\r\n
- \r\n \t
- Tell the employee to:\r\n
- \r\n \t
- Email support@tamus.edu<\/strong><\/li>\r\n \t
- Include ID.me in the subject line<\/li>\r\n \t
- Include their legal name, email and UIN if known<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The A&M System IT Shared Services support team will advise on next steps.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- The employee does not have an SSN, ITIN, international passport, is under the age of 18, or is acting with Power of Attorney.\r\n
- \r\n \t
- Use UIN login for these edge cases.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
Resources<\/h2>\r\nAdministrator ID.me FAQ Document<\/a>\r\n\r\nEmployee ID.me Support Material<\/a>"},{"tab_label":"Email Templates","tab_content":"
Introduction<\/h2>\r\nAdministrators are responsible for directing new employees, retirees, and former employees to ID.me. These email templates provide a starting point for communications with your employees.\r\n
Pre-Employee Template<\/h2>\r\nCongratulations on your new role with [organization]. During your time with [organization] you\u2019ll use The Texas A&M University System Single Sign On (SSO) as a one-stop-shop to login and access services, applications, products and tools.\r\n\r\nAs a pre-employee, you will use ID.me to log into SSO before your start date. A few important things to know before you get started:\r\n
- \r\n \t
- You have exactly 1 ID.me account. Use your existing ID.me account if you already have one.<\/li>\r\n \t
- Your ID.me account is yours, independent of your employment with the A&M System.<\/li>\r\n \t
- Your ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Your ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n<\/ul>\r\nPlease log into SSO using the instructions below.\r\n
- \r\n \t
- Visit the SSO login pageand select the ID.me icon.<\/li>\r\n \t
- Create a new ID.me account or log into your existing ID.me account.<\/li>\r\n \t
- Make sure the following fields in your ID.me account exactly match the information you have already provided us.\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Complete all necessary requirements to obtain a \u201cverified identity\u201d including enabling two-factor authentication.<\/li>\r\n \t
- When asked if you want to release your attributes, select \u201cagree\u201d.\r\n
- \r\n \t
- If you do not select \u201cagree\u201d you will not be able to log into SSO.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- You should be automatically redirected the A&M System SSO menu page.<\/li>\r\n \t
- Reply to this email and let me know that you have successfully logged into A&M System SSO.<\/li>\r\n<\/ul>\r\nIf you experience issues during this process, follow the recommendations below.\r\n
- \r\n \t
- If you have problems with creating, logging into, or updating your ID.me account, review the ID.me troubleshooting guide or contact ID.me support.<\/li>\r\n \t
- If you are able to create\/log into\/update your ID.me account, but are unable to access A&M System SSO, please email support@tamus.edu and include \u201cID.me\u201d in the subject line and your full legal name in the email body.<\/li>\r\n<\/ul>\r\nThank you,\r\n\r\n[Signature]\r\n
Former Employee Template<\/h2>\r\nAs a former employee of [organization], you will no longer log into The Texas A&M University System Single Sign On (SSO) using your [organization] credentials. Instead, you will log into SSO using ID.me.\r\n\r\nA few important things to know before you get started:\r\n
- \r\n \t
- You have exactly 1 ID.me account. Use your existing ID.me account if you already have one.<\/li>\r\n \t
- Your ID.me account is yours, independent of your employment with the A&M System.<\/li>\r\n \t
- Your ID.me account data must exactly match what was provided to the A&M System.<\/li>\r\n \t
- Your ID.me account must meet requirements for a \u201cverified identity\u201d account.<\/li>\r\n<\/ul>\r\nPlease log into SSO using the instructions below.\r\n
- \r\n \t
- Visit the SSO login pageand select the ID.me icon.<\/li>\r\n \t
- Create a new ID.me account or log into your existing ID.me account.<\/li>\r\n \t
- Make sure the following fields in your ID.me account exactly match the information you have already provided us.\r\n
- \r\n \t
- Full Legal Name<\/li>\r\n \t
- SSN<\/li>\r\n \t
- Date of Birth<\/li>\r\n \t
- Gender<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Complete all necessary requirements to obtain a \u201cverified identity\u201d including enabling two-factor authentication.<\/li>\r\n \t
- When asked if you want to release your attributes, select \u201cagree\u201d.\r\n
- \r\n \t
- If you do not select \u201cagree\u201d you will not be able to log into SSO.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- You should be automatically redirected the A&M System SSO menu page.<\/li>\r\n<\/ul>\r\nIf you experience issues during this process, follow the recommendations below.\r\n
- \r\n \t
- If you experience issues creating or updating your ID.me account, review the ID.me troubleshooting guide or contact ID.me support.<\/li>\r\n \t
- If you were able to create\/update your ID.me account, but are unable to log into A&M System SSO, please email support@tamus.edu and include \u201cID.me\u201d in the subject line and include your full legal name and UIN in the email body.<\/li>\r\n<\/ul>\r\nThank you,\r\n\r\n[Signature]"}]}]},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/38474"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2154"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154\/revisions"}],"predecessor-version":[{"id":2465,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2154\/revisions\/2465"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2154"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":2063,"date":"2025-08-14T08:28:01","date_gmt":"2025-08-14T13:28:01","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=2063"},"modified":"2025-10-16T14:07:42","modified_gmt":"2025-10-16T19:07:42","slug":"identity-providers","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/identity-providers\/","title":{"rendered":"Identity Providers"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":35,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-2063","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/IdentityProviders\/IdentityProvidersRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2063","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2063"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2063\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2063"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":2045,"date":"2025-06-10T11:32:39","date_gmt":"2025-06-10T16:32:39","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=2045"},"modified":"2026-06-25T19:27:17","modified_gmt":"2026-06-26T00:27:17","slug":"alerts","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/alerts\/","title":{"rendered":"SSO Alerts"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-2045","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/HomepageMessages\/HomepageMessagesRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2045","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=2045"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/2045\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=2045"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1923,"date":"2025-05-29T08:46:22","date_gmt":"2025-05-29T13:46:22","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1923"},"modified":"2026-06-29T14:42:51","modified_gmt":"2026-06-29T19:42:51","slug":"id-me","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/id-me\/","title":{"rendered":"Using ID.me"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":35,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-page-builder.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1923","page","type-page","status-publish","entry"],"acf":{"page_options":"","custom_page_title":"","banner":{"":null,"banner_options":[],"banner_content":"","background_image":null,"image_overlay_type":"","icon_position":"left","image_overlay_source":null,"svg_source":"","banner_html":"","call_to_action_button":null},"content":[{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":"","column_content":"ID.me is an identity verification service trusted by many federal and state agencies, including the Social Security Administration, Medicare, the IRS, and The Texas A&M University System. To learn more, watch a short video about ID.me<\/a>.\r\n\r\nSee ID.me Frequently Asked Questions<\/a> for more information.\r\n\r\nHow you use ID.me depends on your relationship with the A&M System.\r\n
New Hires, Retirees, and Former Employees<\/h2>\r\n\r\n\r\nStarting November 1st, 2026, pre-hire personnel, retirees, and former employees will no longer use SSO's UIN Login. Instead, these users will be required to use ID.me for authentication with SSO.\r\n\r\nAnyone who already has a valid A&M System credential can use that login; e.g., new student workers and certain retirees.\r\n\r\n"}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p","card","css"],"css_class":"id-me-hi-info-card ","card_link":"","column_content":"
New to ID.me?<\/h3>\r\nYou must have a verified account to use ID.me. First, review ID.me's list of required documents<\/a>. Then, see SSO's Creating an ID.me account page<\/a> to get started. If you need help, visit the Getting Help page<\/a>."}},{"acf_fc_layout":"tab_layout","tab_options":"","css_class":"","tabs_row":[{"tab_label":"Logging in with ID.me","tab_content":"Select the ID.me logo from the Single Sign On (SSO) login page.\r\n
<\/a><\/figure>\r\n\r\n\r\nThe following screen will ask for your Universal Identification Number (UIN) to verify your eligibility to use the ID.me login:\r\n<\/a><\/figure>\r\n\r\n\r\nIf you are eligible to use ID.me, you will be redirected to the ID.me site to log in.\r\n\r\nIf you already have an ID.me account, use your existing username and password to log in.\r\n\r\nOtherwise, create an ID.me account<\/a> and verify your identity with them.\r\n\r\n\r\n\r\nAfter logging into ID.me for the first time, you will authorize A&M System to access your verified identity information. Clicking \u201cDeny\u201d will prevent you from logging in to SSO with your ID.me account.\r\n<\/a><\/figure>"},{"tab_label":"Creating Your Account","tab_content":"<\/a>Creating your ID.me account is easy. You can do it entirely on your own, without assistance from your A&M System HR or benefits representative. View ID.me's step-by-step instructions<\/a>\u00a0or view a step-by-step video<\/a>.\r\n\r\nNOTE: Your ID.me account belongs to you and it is independent of your relationship with the A&M System. You can use it with other entities such as the Social Security Administration, Medicare, and the Internal Revenue Service.\r\n\r\nWhat you need to create your ID.me account:\r\n- \r\n \t
- A smartphone, tablet, or computer with a camera<\/span><\/li>\r\n \t
- Photo ID (U.S. driver\u2019s license or state ID, U.S. passport, or U.S. passport card)<\/li>\r\n \t
- An official government identification number:\r\n
- \r\n \t
- Social Security Number<\/a> (SSN)<\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a> (ITIN)<\/li>\r\n \t
- International Passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n\r\n\r\n\r\nPlease note that the information you provide ID.me must match your legal name, social security number, and birth date in Workday.\u00a0<\/strong>Contact your Human Resources department if a Workday change is needed.\r\n\r\n\r\n\r\nTo create your account:\r\n
- \r\n \t
- Click the ID.me<\/strong> link in SSO<\/li>\r\n \t
- Verify your UIN<\/li>\r\n \t
- Follow ID.me's instructions<\/a> to create your account using:\r\n
- \r\n \t
- Social Security Number<\/a>\u00a0(SSN)<\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a>\u00a0(ITIN)<\/li>\r\n \t
- International passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Set up multi-factor authentication on your ID.me account<\/a><\/li>\r\n<\/ul>\r\nRefer to our Getting Help<\/a> page if you need help creating your account."},{"tab_label":"Getting Help","tab_content":"An excellent resource is\u00a0the Social Security Administration's video about the ID.me account setup process<\/a>.\r\n\r\nFor help with with ID.me, please consult the following links.\r\n
- \r\n \t
- ID.me frequently asked questions<\/a><\/li>\r\n \t
- ID.me required documents<\/a><\/li>\r\n \t
- ID.me account creation step-by-step guide<\/a><\/li>\r\n \t
- ID.me identity verification guides using:\r\n
- \r\n \t
- SSN<\/a><\/li>\r\n \t
- ITIN<\/a><\/li>\r\n \t
- Non-US Passport<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Using a video call with ID.me<\/a><\/li>\r\n \t
- Troubleshooting ID.me issues<\/a><\/li>\r\n<\/ul>\r\n
If you need more assistance, contact us!<\/strong>\r\n- \r\n \t
- ID.me issues<\/strong>: Contact TAMU Help Desk Central\r\n
- \r\n \t
- 979-845-8300 (available 8:00 AM to Midnight)<\/li>\r\n \t
- helpdesk@tamu.edu<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- Single Sign On issues<\/strong>: Contact A&M System Support\r\n
- \r\n \t
- support@tamus.edu<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\r\n\r\n<\/div>"}]},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"
Current Employees<\/h2>\r\nActive employees of the A&M System should use their university\/agency credentials (alternate login)<\/a> rather than ID.me."}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"
Affiliate Users<\/h2>\r\nAffiliates of A&M System members can use ID.me to log in to SSO only if they have a Workday Contingent Worker account<\/strong>.\r\n\r\nAll other affiliates should use the university\/agency credential (alternate login)<\/a> provided by the institution rather than ID.me. This includes contractors, students, and other individuals who work with the A&M System but do not have a Workday account."}},{"acf_fc_layout":"one_column","column_1":{"column_options":["auto-p"],"css_class":"","card_link":null,"column_content":"
Department and Central Administrators<\/h2>\r\nSSO department and central administrators can help new employees, retirees, and former employees learn to use ID.me effectively.\r\n\r\nLearn more about administering ID.me for Single Sign On<\/a>"}}]},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1923"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1923\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1923"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1995,"date":"2025-05-09T10:17:52","date_gmt":"2025-05-09T15:17:52","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1995"},"modified":"2025-10-16T14:07:17","modified_gmt":"2025-10-16T19:07:17","slug":"applications","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/applications\/","title":{"rendered":"Applications"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37507,"featured_media":0,"parent":0,"menu_order":50,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1995","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/ApplicationCodes\/ApplicationCodesRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/37507"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1995"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1995\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1995"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1814,"date":"2024-08-02T16:43:29","date_gmt":"2024-08-02T21:43:29","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1814"},"modified":"2024-08-02T16:45:05","modified_gmt":"2024-08-02T21:45:05","slug":"sso-security-teams","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/sso-security-teams\/","title":{"rendered":"SSO Security Teams"},"content":{"rendered":"
These are the SSO Security team contacts for A&M System member institutions.<\/p>\n","protected":false},"excerpt":{"rendered":"
These are the SSO Security team contacts for A&M System member institutions.<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":35,"menu_order":999,"comment_status":"closed","ping_status":"closed","template":"page-templates\/template-sso-contacts-rss.php","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1814","page","type-page","status-publish","entry"],"acf":{"rss_feed_url":"https:\/\/api.sea.system.tamus.edu\/ws\/rest\/rssdataservice\/Contacts\/SsoSecurityTeamContactRSS"},"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1814"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1814\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1775,"date":"2024-06-03T14:47:36","date_gmt":"2024-06-03T19:47:36","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1775"},"modified":"2025-10-16T13:59:21","modified_gmt":"2025-10-16T18:59:21","slug":"redirects","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/help-system\/key-concepts\/security\/redirects\/","title":{"rendered":"SSO Redirects"},"content":{"rendered":"
\n\n<\/p>\n\nThe Single Sign On site – https:\/\/sso.tamus.edu<\/a> – is the ONLY site authorized to collect your SSO UIN and password.<\/strong>\n<\/div>\n<\/div>\n<\/div>\n\nIf you use a campus or agency federated logon, please educate yourself on the sites and systems authorized to collect that username and password.\n<\/div>\n\nGo to https:\/\/sso.tamus.edu<\/a> now<\/strong>.\n<\/div>\n","protected":false},"excerpt":{"rendered":"The Single Sign On site – https:\/\/sso.tamus.edu – is the ONLY site authorized to collect your SSO UIN and password. If you use a campus or agency federated logon, please educate yourself on the sites and systems authorized to collect that username and password. Go to https:\/\/sso.tamus.edu now.<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":35,"menu_order":1000,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":["post-1775","page","type-page","status-publish","entry"],"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/comments?post=1775"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/1775\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/sso\/wp-json\/wp\/v2\/media?parent=1775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1239,"date":"2021-04-13T17:15:23","date_gmt":"2021-04-13T22:15:23","guid":{"rendered":"https:\/\/it.tamus.edu\/sso\/?page_id=1239"},"modified":"2025-10-16T14:02:26","modified_gmt":"2025-10-16T19:02:26","slug":"application-role-reviewer-responsibilities-new","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/sso\/application-role-reviewer-responsibilities-new\/","title":{"rendered":"Application Role Reviewer Responsibilities"},"content":{"rendered":"
Member institutions must regularly review which of their employees have what roles (privileges) in the various SSO applications, and update those roles to reflect departures or transfers.\u00a0 For example, if an employee had roles in File Depot but is no longer employed by a particular institution, then those roles should be removed.\u00a0 Similarly, if that employee is still employed but has moved to a different position that no longer requires access to FileDepot, then those roles should also be removed.<\/p>\n
If you are an Application Role Reviewer you have one or both of the following\u00a0scopes\u00a0<\/em>of review, depending on what has been assigned to you.<\/p>\n
- \n
- Department level: Responsible for one or more\u00a0Adlocs<\/em>, with a semi-annual review period (January 1st and July 1st).<\/li>\n
- Member level:\u00a0 Responsible for one or more\u00a0system members,\u00a0<\/em>with a more frequent quarterly review period (January, April, July and October 1st).<\/li>\n<\/ol>\n
On the 1st of the month of your quarterly or semi-annually review period, the SSO system will generate a reminder email to\u00a0the system members’ Application Security Officer(s)<\/a> and Application Role Reviewer(s)<\/a> reminding them to perform this required security review.\u00a0 This review should be finished by the 10th of the month.\u00a0 On the 11th day of the review period, the System-wide SSO Member-level Role Verification Report will be sent to the Application Owner and the System Chief Information Security Officer(s).<\/p>\n
Consequences for Missing or Incomplete Reviews<\/strong><\/p>\n
Missing reviews may lead to the loss of administrative role authorizations for the member institution’s \u00a0ASOs, ARRs, and\/or administrative role holders at the institution.<\/p>\n
Additional Documentation\u00a0 (needs removed or updated)<\/strong><\/p>\n
For a visual description of the role review process, view the Security Review Process flowchart<\/a>.<\/p>\n
- Member level:\u00a0 Responsible for one or more\u00a0system members,\u00a0<\/em>with a more frequent quarterly review period (January, April, July and October 1st).<\/li>\n<\/ol>\n
- Department level: Responsible for one or more\u00a0Adlocs<\/em>, with a semi-annual review period (January 1st and July 1st).<\/li>\n
- Single Sign On issues<\/strong>: Contact A&M System Support\r\n
- ITIN<\/a><\/li>\r\n \t
- ID.me required documents<\/a><\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a>\u00a0(ITIN)<\/li>\r\n \t
- Individual Taxpayer Identification Number<\/a> (ITIN)<\/li>\r\n \t
- A smartphone, tablet, or computer with a camera<\/span><\/li>\r\n \t
- Email support@tamus.edu<\/strong><\/li>\r\n \t
- NOTE: If you are a member administrator and need the ID.me Escalation team's email address, contact support@tamus.edu<\/strong>.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
- If this doesn't resolve their issue:\r\n
- Ask the employee to review the ID.me help page<\/a>.<\/li>\r\n \t
- If they ran into an issue when creating a new ID.me account or logging into an existing ID.me account.\r\n
- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Verify the following employee information in Workday and make updates if needed:\r\n
- \r\n
- Visit https:\/\/sso.tamus.edu<\/a><\/li>\r\n \t
- Provide them with these instructions to log into SSO with ID.me\r\n
- When you contact the pre-employee, make sure you explain:\r\n
- The next business day<\/strong>, confirm that the pre-employee\u2019s record was successfully created in SSO by using the SSO Central or Department Administrator role.*\r\n
- Next, create the pre-employee\u2019s record in Workday with as much of the following information as you can:<\/li>\r\n<\/ol>\r\n
- Review the information in UIN Manager and make any necessary updates so that it matches the information provided by the pre-employee.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- If the pre-employee has an existing UIN:\r\n
- Create a new UIN for the pre-employee using the collected information from above.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- If the pre-employee does not have a UIN:\r\n
- Log into UIN Manager and search for the pre-employee\u2019s existing UIN<\/li>\r\n<\/ol>\r\n
- Collect the following information for your pre-employee<\/li>\r\n<\/ol>\r\n
- Given that there are no UIN\/SSN\/EmployeeID conflicts<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- Once an employee\u2019s UIN is assigned to their Workday record:\r\n
- Former employees<\/strong>, including retirees<\/li>\r\n \t
- Pre-employees<\/strong> who need SSO access before their first day<\/li>\r\n \t