Start with a question your team asks regularly, choose the emails, documents or data needed to answer it and connect a compatible MCP or REST client. Preview the shared information and keep important answers open to review.
Supplier update
Delivery is planned for 18 October.
Selected AI context
Let the assistant read the delivery date while prices and original files stay private.
Write down a recurring question such as which supplier delivery dates changed or which invoices are due next. Identify the records and fields needed to answer it.
Choose whether the assistant needs a few fields, readable document text, supporting references or original files. Share only what helps with the question.
Connect the accounts and folders you’re authorized to use. Include the messages and documents needed for the question; import an archive for earlier history and use active connections for later updates.
Open examples to see which text and fields are available before sharing them with the assistant.
Create a shared view of the chosen emails, documents, extracted data or current profiles. In Publication settings, choose Included fields, apply any masking and enable the MCP or REST connection your client supports.
Choose separately whether the assistant can open supporting references or download original files. Set purpose recording and retrieval limits to suit its task.
Include permitted references to the email or document behind a value so a reviewer can check it. Decide separately whether the connection can download the original file.
For invoice due dates, share the invoice references, amounts and dates. Keep unrelated details private and turn off original downloads when the assistant only needs those fields.
Use the intended token to search and read the shared view. Check its visible fields, supporting references and original-file access, with your sharing policies applied.
Choose an AI-context token for one shared view or a catalog token for the eligible views your assistant needs to discover. An existing API-only token needs the appropriate context capabilities before it can use these tools.
Use the latest captured information for a current working view, a schedule for regular updates or a fixed snapshot for a particular review. Capture and refresh details show how recent each version is.
Choose a refresh schedule when new information should reach the assistant regularly. Set up alerts separately when a change should also notify a person.
Check fields used for deadlines, reporting, or customer communication against source evidence. Review and correct extracted working values when needed.
Use the sources and reviewed values to check the assistant’s answer. Review your external provider’s retention and training terms alongside the information you choose to share.
Connect a compatible REST client or an MCP client that can send bearer credentials. Try a known question and check the returned fields, supporting references and freshness information.
To ask questions inside Polytrace, an administrator connects your organization’s AI provider and model. Where the feature is enabled, Ask this publication uses your signed-in access and the same permitted searches and calculations.
Use compatible external clients through the enabled MCP or REST connection with scoped credentials. For questions inside Polytrace, the optional assistant needs deployment enablement, an eligible shared view and your organization’s connected AI provider.
Sharing read-only information through MCP or REST does not call a model in Polytrace. The in-product assistant and model extraction use your organization’s connected provider.
Check important source values and answers before using them for a deadline, customer response, compliance decision, or external report.
Use a compatible client that can send bearer credentials. Direct ChatGPT installation through OAuth needs a separate authorization integration in your deployment; connecting Gmail or enabling company SSO does not supply it.
Choose its information, preview what the assistant can read and check the answer using the intended connection.
