When to use this
AI Assistant:
You have a spec doc, process guide, or requirements document you want the Assistant to reason about alongside your org's metadata
You're working from a Jira ticket, user story, or business requirements doc and want Swantide to understand the context before answering
You want to validate or compare a draft against your existing org configuration
AI Admin:
You're kicking off a build task and have a TDD, ticket, or requirements doc that captures the full design intent
You want to provide context the AI Admin couldn't derive from org metadata alone
Using attachments in AI Assistant
Uploading a document to the AI Assistant allows Swantide to search and rank the content in real time, giving you more precise answers based on your specific materials.
How to upload a document:
Navigate to AI Assistant and start a new conversation.
Click the attachment icon in the chat input.
Select your document and upload.
Type your question — the Assistant will use the document as additional context in its response.
Using attachments in AI Admin
When creating a task in AI Admin, you can attach a TDD, ticket description, requirements doc, or any supporting material so your AI Admin executes your build with the full context from the start.
How to upload a document:
Navigate to AI Admin from the left sidebar.
Create a new task as you normally would — add your title and description.
Click the attachment icon and upload your document.
Submit the task — the AI will reference the attachment throughout the build.
Things to know
File size limit: Documents must be 5 MB or under.
One document per conversation: You can upload one attachment per chat session.
Word doc limitation: If your Word doc contains images, those images will not be processed for context. Convert your file to a PDF before uploading if it contains images.
Supported file types: PDF (.pdf), Word (.docx), plain text (.txt), CSV (.csv), Markdown (.md)
Sample AI Assistant prompts
These prompts assume you've attached the referenced document before sending:
"I've attached a requirements doc for a new lead routing process. Based on what's already in the org, does this design conflict with any existing flows like Lead_Assignment_Process?"
"Review the attached TDD and tell me if any components it references — particularly Case_Escalation_Rule — are configured differently in this org than the design assumes."
"I've attached a user story for updating the Opportunity.StageName picklist. What's the full impact of this change on existing flows and validation rules?"
"Based on the attached spec, write a solution design for implementing this in the org. Flag any components that already exist and could be reused."
Tips
Reference the document explicitly in your prompt. Say "based on the attached spec" or "using the document I uploaded" — this helps the Assistant prioritize that content alongside org metadata.
Pair attachments with specific component names. Instead of "review this doc," try "review this doc and tell me how it relates to Renewal_Process_Handler." Specificity gets better answers.
If your Word doc contains images, convert to PDF first. Image content in .docx files is skipped — use PDF to make sure everything is processed.
For AI Admin: attach your clearest design doc upfront. The TDD quality reflects the clarity of what you give the AI Admin at the start — a well-scoped TDD or Jira ticket goes a long way.
Share your feedback
This feature is in beta and your experience matters. As you start using attachments, we'd love to hear what's working well and where we can improve — your input will directly shape the updates rolling out in the coming weeks.
Reach out to your Swantide rep or email us at support@swantide.com.