> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/updates/release-notes/collaborative-review-comments-and-organization-specific-subdomains.md).

# Collaborative Review Comments & Organization-Specific Subdomains

Our latest updates make access reviews more collaborative and improve platform reliability with customer-specific routing. These enhancements help teams communicate decisions clearly, maintain audit context, and deliver a more secure, scalable experience.

***

#### [Review Comments with Mentions & Campaign Visibility](https://docs.balkan.id/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/collaborating-with-comments-on-reviews.md) *(Early Access)*

Access reviews are no longer siloed across emails and side conversations. Teams can now collaborate directly within reviews—capturing context, resolving questions faster, and maintaining a clear audit trail for future cycles.

**What’s new:**

* **In-Review Collaboration**\
  Reviewers, Risk Managers, and Admins can add comments directly on review items to ask questions, share context, and clarify decisions in real time.
* **Built-In Audit Context**\
  Comments added during approvals, denials, reassignments, and bulk actions are automatically captured—keeping decision reasoning tied to the review itself.
* **Rich & Smart Communication**\
  Format comments with rich text and use @mentions or notify all reviewers to bring the right people into the discussion instantly.
* **Campaign-Level Oversight**\
  Risk Managers and Admins can view aggregated comments across Reviewers, Integrations, and Resources from the Campaign Summary—making it easier to track progress and spot blockers.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F9WyUqNOGgxI9dUe64UbF%2Fimage.png?alt=media&amp;token=56db5e83-9c6d-42b5-94a2-dd7bdea9748b" alt=""><figcaption></figcaption></figure></div>

***

#### [Organisation-Specific Application Subdomains](https://docs.balkan.id/getting-started/user-onboarding/balkanid-onboarding.md)

As part of our ongoing commitment to improving your experience and strengthening platform security, we’ve rolled out **dedicated subdomains for each organisation**.

You can now access your organisation in either of the following ways:

* **Direct access:** Navigate directly to `https://[organization].app.balkan.id`.
* **Central access:** Go to `https://app.balkan.id`. You’ll be prompted to enter your organisation name, after which you’ll be redirected to your organisation’s login page.

**What this means for you:**

* **Dedicated routing per customer**\
  Each organisation now operates on its own secure subdomain (for example, `examplecorp.app.balkan.id`). This improves isolation, reliability, and long-term scalability—helping ensure your environment remains fast, stable, and secure as we grow together.
* **A refreshed login experience**\
  Along with dedicated subdomains, you’ll see a more streamlined login experience designed to be clearer, faster, and more secure from the moment you sign in.

{% hint style="info" %}
The new subdomains do not affect which tenants you can access, or the roles and permissions you have today. Contact BalkanID support in case you have a question
{% endhint %}

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2F9BEd5URu68TOWMAT0Pfn%2Fimage.png?alt=media&amp;token=f71ef6da-25dc-454e-b260-494d569c4d6c" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/updates/release-notes/collaborative-review-comments-and-organization-specific-subdomains.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
