How do I separate SeleID test and live work?

Decide which accounts and datasets are safe for testing. Use synthetic data and separate test credentials where available. Review the target environment before every deployment or migration. If test activity appears in live logs, stop the test and check the endpoint, credential and project settings.

If test activity appears in live logs, stop the test and check the endpoint, credential and project settings. Decide which accounts and datasets are safe for testing. If you need help, include the product you were using and the step that failed. Keep passwords, one-time codes and secret keys private.

Keep development credentials, callback URLs and data separate from live use. Check each SeleID product’s documentation for a supported test mode or sandbox before relying on one. If a product exposes separate environments to your workspace, label them clearly and confirm the environment before making changes.