Account security and phone-number verification
Open Account settings, verify an optional phone number when available, and distinguish sessions from project and MCP permissions.
Manage sign-in and security in Altifigence Account. A signed-in app, a confirmed phone number, project membership and an MCP grant are separate access states.
Open the intended account
From the app's signed-in account menu, open Settings → Account & security.
Check the account and security status. Use the relevant Manage link to open the Account portal.
Confirm the account again before changing a sign-in method. Use only the methods offered by the current portal.
Confirm an optional phone number
In Settings → Account & security, use the phone-number Manage or Open phone settings link. It opens https://account.altifigence.com/manage#phone.
If registration is offered, choose Add number or Change and read the text-message provider and privacy notice before sending a number.
Enter a number with its + country code. Check the destination carefully.
Complete the fresh check of an existing sign-in method when requested, then use Send code.
Enter the text-message code in the Account portal and choose Confirm number. Never paste the code into a chat or support ticket.
Check that the portal reports Confirmed. Only a confirmed number is saved; sending a code alone does not complete registration.
Availability depends on the account service. If the app or portal says registration is unavailable, stop there and check later. This guide covers phone-number confirmation, which does not by itself grant a project role, an engine or an MCP tool.
A code is missing or expired
Message | Action |
|---|---|
Invalid number | Use the international +country-code format and check the digits. |
Code expired | Restart the offered verification flow and use its current code. |
Too many attempts | Wait for the displayed retry window rather than repeatedly sending codes. |
Verification unavailable/conflict | Keep the current account and sanitized error; refresh the portal before another change. |
Review sign-in methods and sessions
Use the offered passkey, authenticator or provider setup and complete its verification before treating it as active.
If recovery codes are provided, keep them privately outside chat, source control and diagnostic reports.
Open the account's session/security view and identify the current session.
Review unfamiliar or unused sessions and use the offered revocation control if appropriate. Device/location labels can be approximate.
After revocation, affected apps or MCP connections can require sign-in again. Verify the intended account.
Find the right access problem
Problem | Where to check |
|---|---|
Cannot sign in | Account method and offered verification/recovery route |
Project missing | Selected organization and accepted membership |
Desktop tool unavailable | Installed version and the selected operation's host capability |
MCP tool denied | Current organization tool policy, granted scopes and fresh consent |
Usage limit | Current organization's Usage and effective caps |
For support, retain the product version, time and sanitized message. Do not send passwords, passkey material, one-time codes, recovery codes, session cookies or API keys.
Related guides
First launch · MCP authentication · Cloud projects
Adding a phone number is optional and does not create a sign-in method. Email-and-text account recovery is not available yet; confirming a number does not enable it.