> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/trust-access/application-access-governance-preview/register-an-application.md).

# Register An Application

Register and configure a new application within TrustLogix for access policy enforcement , follow the steps outlined below. This configuration provides the necessary credentials (Client ID, Client Secret, etc.) required for the consumption side to evaluate defined access policies via API.

### Create a New Application

First, navigate to the Applications management section of the TrustLogix platform to initialize the registration.

* Navigate to: <https://dev.trustlogix.io/app/applications>.
* Click the "Create Application" button.
* Enter the Application Name: Click the "Application Name" field and type your desired name (e.g., "Finance Analysis").
* Enter a Description: Click the "Description" field and provide details for the application (e.g., "Finance Analysis").
* Save: Click "Save" to create the entry.

***

### Configure Service Principal Details

Once the application is created, you must configure its Service Principal details. These values are essential for the consumption side to authenticate before calling the policy evaluation API.

***Prerequisites***

***Configure the IdP Application Details***

> *Create a separate application to integrate the graph endpoint as source in TrustLogix. Please follow* [*prerequisites*](https://docs.trustlogix.io/integrations/attribute-source-connection/azure-ad-or-ms-entra-graph-endpoint#id-3.-follow-the-prerequisite-steps) *step to get the required details to complete the integration.*

> *Get Application(Client) ID and Directory(Tenant) ID from Azure Application Overview page.*
>
> *Copy Secret value while creating in prerequisites step.*

* Select the Application: From the application list, click on the newly created application name (e.g., "Finance Analysis").
* Access Configuration: Click on the "Configuration" tab located in the top menu.
* Fill Service Principal Details:
  * Client ID: Enter the unique identifier for the application.
  * Client Secret Value: Enter the secret key associated with the application.
  * Application Scope: Define the scope required for the application's access.
  * Token Endpoint: Enter the URL endpoint used to retrieve authentication tokens.

***

### Finalize Registration

* Save Configuration: Click "Save" at the bottom of the Configuration page to store the service principal details.
* Confirmation: Ensure the "Application created successfully" notification appears.

Note: Only applications with an "Active" status can be targeted by new Access Policies. Ensure the toggle for "Application Status" is enabled during configuration.

\
\ <br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trustlogix.io/trust-access/application-access-governance-preview/register-an-application.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.