> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/reference/settings/data-onboarding/portal-settings.md). # Portal settings Portal settings decide where suppliers sign in, how they sign in, and how often they review their team. Portal settings can be updated through Settings > Data onboarding > Portal settings. ## Portal address ### Supplier portal URL The address where your suppliers sign in. Suppliers get this link in their invite email. Copy it to share it directly, or click **Open portal** to open the portal yourself. ## Sign-in security ### Require two-step verification for all supplier users When turned on, supplier users must enter a code after their password. Users who have not set it up are signed out, and set it up at their next sign-in. Off by default. ### Allowed methods * **Email code**: a six-digit code sent to the user's email address * **Authenticator app (TOTP)**: a code from an app such as Microsoft Authenticator At least one method is required. Removing a method does not sign out users who already verified with it. ### Remember a browser for How many days a supplier can skip the code on a browser they choose to remember. From 0 to 90 days, 30 by default. 0 turns the option off. ## Team review ### Ask supplier admins to review their team list regularly When turned on, each supplier's admins are regularly asked to confirm who on their team should keep access. Off by default. ### Review every The number of days between reviews. At least 14, 90 by default. Supplier admins are reminded 14 days before a review is due, and again when it is overdue. ### First review Shown when team reviews are turned on. Choose whether everyone is due now, or one interval after each supplier was created. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.struct.com/reference/settings/data-onboarding/portal-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.