> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/administration.md). # Administration ## Overview The Administration module is where administrators manage AttackForge. It has two purposes: * **Track and manage your licensing.** * **Configure and customise your tenant**, so AttackForge fits the way your team works. {% hint style="info" %} Only Administrators can open the Administration module. {% endhint %}
## Administration areas | Group | Area | What you configure | | --------------------- | ------------------ | ----------------------------------------------------------- | | **Licence** | Licence | Licence type, plan and end date; credits; subscriptions | | **Data and modules** | Portfolios | Settings for Portfolios | | | Projects | Settings for Projects | | | Project Requests | Settings for Project Requests | | | Vulnerabilities | Settings for Vulnerabilities | | | Project Test Cases | Settings for Project Test Cases | | | Retesting | Settings for Retesting Rounds | | | Reporting | Settings for Reporting | | | Pages | Settings for Project Pages | | | Groups | Settings for Groups | | | Assets | Settings for Assets | | | Writeups | Settings for Writeups | | | Test Suites | Settings for Test Suites | | **People and access** | Users | Settings for Users | | | Login and Security | Login, SSO and security settings | | | Notifications | Settings for Notifications | | **Your tenant** | Integrations | Your integrations | | | Preferences | Miscellaneous settings, including a custom logo and colours | ## Why it matters * **AttackForge works the way you do.** Match fields, workflows and reports to your methodology, clients and teams. * **Consistent data.** Settings apply across every project, so everyone records findings the same way. * **Secure access.** Control how people sign in and what they can do. * **No surprises on licensing.** See your plan, end date and credits in one place. ## Who uses it | Who | To | | ------------------------------- | ------------------------------------------------------------------------------------- | | **Administrators** | Configure the tenant, manage users, security and integrations | | **Security and practice leads** | Decide how projects, findings, retests and reports should work, with an administrator | | **Finance or account owners** | Check the licence, credits and subscriptions | ## Licence See an overview of your licence, including: * **Licence type, plan and end date.** * **Credits:** how many you've used and how many are left, and the option to top up. * **Subscriptions:** the ability to enable or disable subscriptions. Check this area before a renewal, or when you plan a busy period of testing, so you don't run out of credits. ## Data and modules These areas control how each part of AttackForge works across your tenant. Each links to the page that explains the feature. Across these areas, settings often include custom fields, default values and the options people can choose. ### Portfolios Configure settings for Portfolios. See [Portfolios](https://support.attackforge.com/app/modules/portfolios). ### Projects Configure settings for Projects. See [Projects](https://support.attackforge.com/app/modules/projects). ### Project Requests Configure settings for Project Requests, such as the form people fill in to request testing. See [Requesting a project](https://support.attackforge.com/attackforge-enterprise/getting-started/requesting-a-project). ### Vulnerabilities Configure settings for Vulnerabilities. See [Vulnerabilities](https://support.attackforge.com/app/modules/vulnerabilities). ### Project Test Cases Configure settings for Project Test Cases. See [Test cases](https://support.attackforge.com/attackforge-enterprise/getting-started/test-cases). ### Retesting Configure settings for Retesting Rounds. See [Retesting](https://support.attackforge.com/app/getting-started/retesting). ### Reporting Configure settings for Reporting. See [Reporting](https://support.attackforge.com/app/getting-started/reporting) and the [Reporting overview](https://support.attackforge.com/app/modules/reporting/overview). ### Pages Configure settings for Project Pages. See [Project pages](https://support.attackforge.com/app/getting-started/project-pages). ### Groups Configure settings for Groups. See [Groups](https://support.attackforge.com/app/modules/groups). ### Assets Configure settings for Assets. See [Assets](https://support.attackforge.com/app/modules/assets). ### Writeups Configure settings for Writeups. See [Writeups](https://support.attackforge.com/app/modules/vulnerability-library). ### Test Suites Configure settings for Test Suites. See [Test Suites](https://support.attackforge.com/app/modules/testsuites). ## People and access ### Users Configure settings for Users. See [Users](https://support.attackforge.com/attackforge-enterprise/modules/users) and [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access). ### Login and Security Configure login, single sign-on (SSO) and security settings. Use it to control how people sign in to AttackForge. ### Notifications Configure settings for Notifications. See [Notifications](https://support.attackforge.com/attackforge-enterprise/getting-started/notifications). ## Your tenant ### Integrations Configure your [SecDim](https://support.attackforge.com/app/modules/writeups#help-developers-fix-issues-with-secdim-sandboxes) and [AI MCP](/app/automations-and-integrations/ai-mcp-and-skills.md) integrations. For automations and connections to other tools, see also [Flows](https://support.attackforge.com/app/automations-and-integrations/flows), [Actions](https://support.attackforge.com/app/automations-and-integrations/actions) and the [Self-Service RESTful API](https://support.attackforge.com/app/automations-and-integrations/self-service-restful-api). ### Preferences Configure miscellaneous settings, including a custom logo and colours. Use it to brand AttackForge for your organisation. ## Tips * **Plan changes before you make them.** Settings apply to the whole tenant, so agree changes with the people who use them. * **Make one change at a time,** and check the result on a test project before you rely on it. * **Check the Licence area regularly,** especially before renewals and busy testing periods. * **Set up Login and Security first** when you onboard a new tenant, before you invite users. * **Brand your tenant** in Preferences, so clients and testers recognise it. * **Keep a record of your settings,** such as a screenshot or note, so you can restore them if something changes. ## FAQ **Who can use Administration?** Administrators. **Where do I see my licence end date?** In the Licence area, with your licence type and plan. **How do I get more credits?** Top up in the Licence area. **Can I turn subscriptions on and off?** Yes, in the Licence area. **Where do I set up single sign-on?** In Login and Security. **How do I add my logo?** In Preferences. **Do settings apply to existing projects?** It depends on the setting. ## Related pages * [Concepts and Access](https://support.attackforge.com/app/getting-started/concepts-and-access) * [Portfolios](https://support.attackforge.com/app/modules/portfolios) * [Projects](https://support.attackforge.com/app/modules/projects) * [Vulnerabilities](https://support.attackforge.com/app/modules/vulnerabilities) * [Groups](https://support.attackforge.com/app/modules/groups) * [Assets](https://support.attackforge.com/app/modules/assets) * [Writeups](https://support.attackforge.com/app/modules/vulnerability-library) * [Test Suites](https://support.attackforge.com/app/modules/testsuites) * [Reporting overview](https://support.attackforge.com/app/modules/reporting/overview) * [Flows](https://support.attackforge.com/app/automations-and-integrations/flows) --- # 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://support.attackforge.com/app/modules/administration.md?ask=&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.