> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/event-contributor-portals/speaker-portal.md).
# Speaker Portal
Give your Speakers agency and lower your own workload
The Speaker Portal is a tool that allows Speakers to update important information about their sessions without the need to contact an event organiser to do it for them. This means that any changes or updates to a session can be done quickly and easily.
The Speaker Portal is accessible by enabling the setting Enable speaker content editing. This will enable people to access the portal and make edits to the talks they are linked to. It is also possible to set a deadline after which submissions are no longer possible.
Once the portal is active, a new email draft is added to the Mail overview. This mail is set to be sent to Speakers and contains a personalised link to the Speaker Portal. This can be sent as a direct message, or scheduled, as well as being edited prior to being sent.
The Sessions overview shows the list of sessions that a Speaker is connected to. Speakers can see when it takes place and the status of any changes that have been requested.
When editing talk it is possible to modify a session's title, description, and image. In addition to this, sessions which have been edited have show their status and if they have been rejected, the reason that changes are required.
When a session change is accepted or rejected, the speaker receives an email detailing the decision. For accepted changes, the status changes back to open until the deadline passes or another submission is submitted
---
# 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://knowledge-base.letsgetdigital.com/event-contributor-portals/speaker-portal.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.
