See Creating Your Account<\/a> and ID.me Frequently Asked Questions<\/a> for more information.<\/p>\n\n\n\n Your ID.me account belongs to you and is independent of your relationship with the A&M System. 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. What you need:<\/p>\n\n\n\n Please note that the information you provide ID.me must match your legal name, social security number, and birth date in Workday.<\/strong><\/p>\n\n\n\n To get started, click the ID.me link in SSO, verify your UIN, and follow ID.me’s instructions to create your account and set up multi-factor authentication.<\/p>\n\n\n\n ID.me Resources:<\/strong><\/p>\n\n\n\n ID.me is a next-generation digital identity network that simplifies how individuals securely prove their identity online. ID.me’s technology meets federal standards for consumer authentication set by the Department of Commerce and is approved as a NIST 800-63-3 IAL2\/AAL2 credential service provider by the Kantara Initiative. ID.me is committed to \u201cNo Identity Left Behind\u201d to enable all people to have a secure digital identity. Learn more about ID.me<\/a>.<\/p>\n\n\n\n Yes. In fact, you should have only one account with ID.me. Your ID.me account belongs to you and is completely independent of your employment or retirement relationship with the A&M System.<\/p>\n\n\n\n Please note that you may need to verify additional information with ID.me to use your account with SSO. This process is similar to creating a new account<\/a>.<\/p>\n\n\n\n Your privacy is important to the A&M System and ID.me, and they make it a priority to protect and safeguard your information. ID.me will not sell, rent or trade your personal information. ID.me supports more than 20 languages in its Self-Service support and over 240 languages in video chat. You might not be able to complete your verification because of account sign-in issues, a duplicate account or trouble uploading your documents. Visit I couldn\u2019t verify my identity<\/a> or I can\u2019t sign in to my account<\/a> for help with completing verification.<\/p>\n\n\n\n You can change or add email addresses, update your password and more at account.id.me<\/a>. To learn how, visit Managing your ID.me account settings<\/a>.<\/p>\n\n\n\n No, you can only have one verified ID.me account. The account is tied to you as an individual, similar to having one driver\u2019s license or Social Security number. If you think you have multiple accounts, you can troubleshoot at What to do if you have a duplicate account<\/a>.<\/p>\n\n\n\n After you complete the verification process for the first time, you\u2019ll receive an email from ID.me confirming that your identity has been successfully verified. If you used your existing ID.me login to share your identity information with a new organization, you\u2019ll receive a text message from ID.me confirming you used your account to access an organization. To see which organizations you\u2019ve shared your identity information with, visit Finding who you shared your information with<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" ID.me is an identity verification service trusted by many federal and state agencies, including The Texas A&M University System. Pre-hire personnel, retirees, and former employees will use ID.me for authentication with SSO. NOTE: Active employees of the A&M System should use their university\/agency credentials (alternate login). See Creating Your Account and ID.me Frequently Asked Questions […]<\/p>\n","protected":false},"author":37526,"featured_media":0,"parent":35,"menu_order":0,"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":{"0":"post-1923","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1923","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/37526"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1923"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1923\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/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:\/\/tamuserp2.wpengine.com\/sso\/applications\/","title":{"rendered":"Applications"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":37526,"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":{"0":"post-1995","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1995","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/37526"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1995"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1995\/revisions"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/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:\/\/tamuserp2.wpengine.com\/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":{"0":"post-1814","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1814"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1814\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/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:\/\/tamuserp2.wpengine.com\/sso\/help-system\/key-concepts\/security\/redirects\/","title":{"rendered":"SSO Redirects"},"content":{"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":{"0":"post-1775","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1775"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1775\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/35"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/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:\/\/tamuserp2.wpengine.com\/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 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 Application Role Review Process Details<\/strong><\/p>\n Following is a suggested procedure for this process:<\/p>\n If you are responsible for both Department and Member level reviews, you will have to repeat the above process for each scope of review.<\/p>\n Congratulations!\u00a0 You have finished your SSO Application Role Review.\u00a0 These reviews will remain in the SSO Role Review application and will be subsequently verified by your workstation’s Application Security Officer\u00a0<\/em>on or after the 11th of the month.<\/p>\n","protected":false},"excerpt":{"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 […]<\/p>\n","protected":false},"author":41,"featured_media":0,"parent":0,"menu_order":35,"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":{"0":"post-1239","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1239","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/41"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1239"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1239\/revisions"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/media?parent=1239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1203,"date":"2020-12-04T12:31:41","date_gmt":"2020-12-04T18:31:41","guid":{"rendered":"http:\/\/it.tamus.edu\/sso\/?page_id=1203"},"modified":"2025-04-03T08:01:49","modified_gmt":"2025-04-03T13:01:49","slug":"using-the-employee-monthly-position-changes-report","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/sso\/help-system\/key-concepts\/administrator-navigation\/reports\/employee-monthly-position-changes\/using-the-employee-monthly-position-changes-report\/","title":{"rendered":"Using the Employee Monthly Position Changes Report"},"content":{"rendered":" The “Employee Monthly Position Changes” report can be generated at any time, but it is primarily run during the Member-level Role Review Process and the Department-level Role Review Process.<\/p>\n The report returns a list of employees who currently have access to the selected Workstation for the selected Application(s). It also includes information about the employee’s current and previous position.<\/p>\n Tip: If this report is going to be downloaded and filtered\/sorted, save it as \u00a0CSV (comma delimited) format. This strips out the formatting and titles.<\/p>\n Here are the parameters used for this report.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" The “Employee Monthly Position Changes” report can be generated at any time, but it is primarily run during the Member-level Role Review Process and the Department-level Role Review Process. The report returns a list of employees who currently have access to the selected Workstation for the selected Application(s). It also includes information about the employee’s […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":1199,"menu_order":0,"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":{"0":"post-1203","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1203","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1203"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1203\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1199"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/media?parent=1203"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1199,"date":"2020-12-04T12:18:48","date_gmt":"2020-12-04T18:18:48","guid":{"rendered":"http:\/\/it.tamus.edu\/sso\/?page_id=1199"},"modified":"2021-05-10T10:48:19","modified_gmt":"2021-05-10T15:48:19","slug":"employee-monthly-position-changes","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/sso\/help-system\/key-concepts\/administrator-navigation\/reports\/employee-monthly-position-changes\/","title":{"rendered":"Employee Monthly Position Changes"},"content":{"rendered":" The ‘Employee Monthly Position Changes’ report is available to Central Admin roles and the Workstation parameter is based upon the user’s access. All parameters are required to run this report.<\/p>\n The report will generate a list of employees that have a role in the chosen application with access to the chosen Workstation and have had a position-related change such as a Position ID (PIN) or job title change or a hire\/termination event.<\/p>\n It is recommended that this report be run on a regular basis to ensure that access privileges of inactive employees are removed in a timely manner.<\/p>\n Click here to learn about using this report.<\/a><\/p>\n The ‘Employee Monthly Position Changes’ report is available to Central Admin roles and the Workstation parameter is based upon the user’s access. All parameters are required to run this report. The report will generate a list of employees that have a role in the chosen application with access to the chosen Workstation and have had […]<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":122,"menu_order":4,"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":{"0":"post-1199","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1199","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/comments?post=1199"}],"version-history":[{"count":0,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/1199\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/pages\/122"}],"wp:attachment":[{"href":"https:\/\/tamuserp2.wpengine.com\/sso\/wp-json\/wp\/v2\/media?parent=1199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":1155,"date":"2020-09-09T20:23:43","date_gmt":"2020-09-10T01:23:43","guid":{"rendered":"https:\/\/tamuserpstage.wpengine.com\/sso\/?page_id=1155"},"modified":"2025-10-16T14:01:01","modified_gmt":"2025-10-16T19:01:01","slug":"sso-applications-and-integrations-working-group","status":"publish","type":"page","link":"https:\/\/tamuserp2.wpengine.com\/sso\/sso-applications-and-integrations-working-group\/","title":{"rendered":"SSO Applications and Integrations Working Group"},"content":{"rendered":" The SSO Applications and Integrations Working Group reviews, discusses and proposes solutions to known application and integration issues submitted by members. The Financial Systems Council will review, discuss, and approve items requiring significant development projects.<\/p>\n Working Group Chair: Marc Moore<\/a><\/p>\n <\/p>\nLogging in with ID.me<\/h2>\n\n\n\n
\n
![\"Screen](\"https:\/\/tamuserp2.wpengine.com\/sso\/wp-content\/uploads\/sites\/4\/2025\/05\/IDme_logo-274x300.png\"){kind=logo}
<\/a><\/figure><\/li>\n\n\n\n
If you already have an ID.me account, use your existing username and password to log in.
Otherwise, create an account and begin verifying your identity.<\/li>\n\n\n\n![\"Screen](\"https:\/\/tamuserp2.wpengine.com\/sso\/wp-content\/uploads\/sites\/4\/2025\/05\/IDme_homescreen-167x300.png\")
<\/a><\/figure><\/li>\n<\/ol>\n\n\n\nCreating Your Account<\/h2>\n\n\n\n
\n
\n
ID.me Frequently Asked Questions<\/h2>\n\n\n\n
What is ID.me?<\/h3>\n\n\n\n
I already have an ID.me account. Can I use it with SSO?<\/h3>\n\n\n\n
Will ID.me sell my information?<\/h3>\n\n\n\n
Learn about the ID.me Privacy Center<\/a>.<\/p>\n\n\n\nCan I verify my identity in a language other than English (Haitian Creole, Mandarin, Spanish, etc.)?<\/h3>\n\n\n\n
Learn more about verifying in a language other than English<\/a>.<\/p>\n\n\n\nI\u2019m having trouble verifying my identity or signing in to my ID.me account. How do I get help?<\/h3>\n\n\n\n
How do I update my ID.me account?<\/h3>\n\n\n\n
Can I have more than one ID.me account?<\/h3>\n\n\n\n
How do I know I successfully verified my identity?<\/h3>\n\n\n\n
![\"Notification](\"https:\/\/sso.tamus.edu\/Resources\/Images\/ssolock.png\")
<\/p>\n\n
\n
\n
\n
\n(For\u00a0Departmental\u00a0<\/em>reviews, set the time period to 6 months;
\nFor\u00a0System\u00a0<\/em>reviews, set the time period to 3 months)<\/li>\n\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
![\"Employee](\"https:\/\/tamuserp2.wpengine.com\/sso\/wp-content\/uploads\/sites\/4\/2020\/12\/Employee-Monthly-Position-Changes-report-example.png\")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Members<\/h2>\n