Why this matters
A database, database user and application configuration must refer to the intended project.
Step by step
- Identify the application and its database requirements without exposing passwords in your request.
- Use the available database tools with authorised permissions or ask the administrator to create scoped credentials; keep them out of public files.
- Test the application’s database-dependent function without granting unnecessary access to other databases.
Keep the result of the final check and any unresolved question with your project records.
Availability depends on the product, permissions and management agreement. Use the existing support conversation for the same issue.
