Account and access questions
These answers help distinguish your personal account, project administration access and customer registration.
Why can I sign in to one environment but not another?
Administration accounts belong to an environment. Check whether the account exists in the intended development, staging or production access list. An account created in development does not automatically create its production counterpart.
Also check the service address: the personal OWOXO account, an application’s customer account and a back-office account serve different sign-in journeys. Identify the environment and account type before resetting a password or creating another account.
Does switching projects merge their records?
No. It changes the selected working context. Confirm the project name before editing its settings, offer or application.
For example, two projects can both have a customer area while keeping separate requests, offers and installations. The selected name, rather than a similar area label, identifies the records concerned. Return to the correct project before making the change.
Why is there no public registration link?
The application can disable public account creation. The same policy blocks the registration page, so opening its address directly does not bypass the decision. Follow the service owner's account-opening process.
A service can require a review of customer information before opening an account manually. In that case, the missing public entry is consistent with the chosen opening process. Administration access is a different process and does not replace the customer account.
Does disabling registration delete existing accounts?
No. The registration policy controls public creation. Existing accounts and their permissions are managed separately by the application's account tools.
After changing the policy, check the public link and the direct registration page in the same environment. Manage an existing person’s access through the relevant account tools; changing the registration rule alone is not an account-removal action.
Can I delete the project owner from the access list?
The owner is protected from removal through this screen. Ordinary account actions also do not apply to protected test accounts. Use the available password reset when the need is to maintain an existing access.
Identify whether the intended task is to maintain the owner’s login or remove an ordinary member. The available actions follow the account’s protection. A missing delete action should not be interpreted as permission to remove the same protected account through another route.
Does an empty access list mean the project has no users?
It concerns the selected environment's administration accounts. It does not list every customer in your application's own business records. Check the project, environment and loading state before drawing a conclusion.
An empty recorded list and an unavailable list are different situations. Read the loading or setup message, then confirm the selected installation. Customer business records must be reviewed in the application’s own tools, rather than inferred from this administration list.