# Profile ID Rules * By default, a Profile URL should be resolved into a service and a username * If the user is reachable by EITHER a username or a user\_id, then use the username as the service\_id. * If the user is reachable only by a series of numbers, then place this series of numbers in the username field. * If the user's profile is only reachable by a combination of a username and another attribute, such as a user\_id or a subdomain, put the subdomain in the user\_id field, and the username in the username field. * If a URL is parsable by the SocialUrlParser, is should be generatable by the SocialUrlGenerator. * If a service is listed in the SocialUrlParser, there must be a list of Ids to reject in the Bax::Data::Store::Profiles folder. * If a service is listed in either the the SocialURLParser or Generator, it's service must be listed in the global\_service\_keys mixin (Bax::Mixins::SocialParsingData. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://omalab.gitbook.io/engineeringwiki/working/profiles-and-enrichment/profile-id-rules.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.