> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/configure-access-by-role/configure-a-project.md).

# Configure a Project

In your applications you can define user roles on the project configuration pages in the Designer. In the example below the role 'testers' is added to 'My application'.

1. Go to the project overview page and click ***Modify***.
2. In the *Security* section, set "Require Authentication" to "Yes" to require users to log in before accessing your application. When you enable authentication the system will display an area where you can create roles.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-92b085546a32551dafbb7abc140368b91ab5e860%2F2c97ca41-205c-49c8-907d-b5f30ec6ff2d.png?alt=media)
3. Create the roles that you want to associate with your application. Add a new role by clicking ***new***. Enter the role name and click ***save***.

   ![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f6bba530f2f5927a095e35b0711473fcae368302%2F8c202cc1-f27c-4a2d-9390-fde5c7d3c497.png?alt=media)
4. Save the changes to your project settings by clicking ***save*** at the top of the screen.
5. Publish your project. You must publish your application to make it visible in the user management function and to allow you to assign roles to your users.


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/user-management/configure-access-by-role/configure-a-project.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.