How to use Projects
Creates an architecture project, level, repository context and membership.
What this section is for
Creates an architecture project, level, repository context and membership.
Before you start
You need access to IAM.Solution / AGL, the correct tenant/workspace and permission to change this configuration. Prepare a non-sensitive example value such as customer-portal-demo.
Buttons and forms
| Control | What it does |
|---|---|
| Create project | Opens the creation flow. The object is not persisted until the final save action. |
| Architecture level | Performs the action named in the interface. Review the resulting state or message before continuing. |
| Open | Opens the selected record and its available evidence or configuration. |
| Archive | Performs the action named in the interface. Review the resulting state or message before continuing. |
Primary path in the interface
- Open the application link above and sign in with the least-privileged role required for this section.
- Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
- In the navigation, click Projects. The expected address is https://app.iamsolution.ru.
- Click Create project. Enter the documented safe values:
customer-portal-demo. Do not paste a production secret into a free-text field. - Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
- Review the validation message or changed row. The result must match this purpose: Creates an architecture project, level, repository context and membership.
- Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.
Second path: direct link and CLI/API
- Open the deep link https://app.iamsolution.ru instead of navigating through the sidebar.
- Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
- Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:
agl --help
agl validate ./architecture.agl
agl render ./architecture.agl --format svg --output ./out/architecture.svg
How to verify the result
The project has a stable ID, selected architecture level and opens for assigned members.
If it did not work
| Symptom | What to do |
|---|---|
| 401 / sign-in screen | Sign in again, then return to this page. Do not put a session token in a URL. |
| 403 | Check the selected tenant and request the documented role; retrying with the same role will not help. |
| 404 | Verify the exact path and whether the feature is enabled in this environment. |
| 409 | Search for an object named customer-portal-demo; continue with it or choose a unique name. |
| 422 / validation error | Correct only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise. |
| 429 | Wait for the displayed retry interval or reduce the request scope; do not start parallel retries. |
| 5xx / timeout | Refresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support. |