Overview
Structur's rich text editor is where your company's internal knowledge lives. It's the tool you use to create the documents that hold your business together, standard operating procedures, training materials, company policies, project documentation, and knowledge base articles, all stored and accessible inside the platform your team is already working in.
Instead of managing separate Google Docs, Word files, or PDF libraries that live outside your workflow, rich text pages let you build and maintain internal documentation right inside Structur. The editor gives you the formatting tools to produce clean, structured, professional content that your team can follow and reference without leaving the platform.
Understanding Rich Text
What It Does
Structur's rich text editor allows you to:
Create structured documents with headings to organize information clearly and make long documents easy to navigate
Use bulleted and numbered lists to break down steps, requirements, or grouped information into scannable formats
Apply text formatting, bold, italic, underline, and highlight, to call out key terms, warnings, and important details
Embed multimedia - insert images, GIFs, and YouTube videos to make training materials and guides more visual and engaging
Produce any type of internal document your business needs, including:
Standard Operating Procedures (SOPs) - step-by-step instructions for any repeatable process
Training Materials - comprehensive guides and tutorials for onboarding and ongoing team development
Company Policies - clear documentation of rules, expectations, and standards
Project Documentation - detailed records of project plans, progress, and outcomes
Knowledge Base Articles - a library of reference articles on any topic relevant to your business
When to Use It
Rich text pages are the right tool when you need to:
Document a process your team needs to follow consistently, anything from how to run a job kickoff meeting to how to submit a change order
Create training content for new hires that they can reference on their own without needing the owner or manager to explain it each time
Write out company policies in a format that can be shared with and signed off by all team members
Build a searchable internal knowledge base so your team can find answers independently
Record project-specific documentation that needs to be detailed, structured, and stored alongside the project record
Step-by-Step Instructions
1. Navigate to the Standard Operating Procedures
From your Structur dashboard, click on the Company Operations menu
Navigate into Standard Operating Procedures area
This is the section of Structur where all internal documentation and company knowledge lives.
2. Navigate to the Right Section
Within the SOPs area, select the department relevant to the document you're creating
Then create the new page.
For example, if you're creating an SOP for your estimating process, navigate to the folder for your Estimator and create the new page within this department.
Taking a moment to put the page in the right location from the start keeps your documentation organized and easy to find later.
3. Add a New Page
Once you're in the correct department, click New Page
Insert the page name and set privacy settings
4. Create "Rich Text" content
From the new page created, click on “New Element” to add the Text content type.
Select New Text
Give the new content type, a title and a description
Good title examples:
"Subcontractor Onboarding Checklist"
"How to Submit a Change Order"
"Safety Inspection SOP - Pre-Construction"
"New Employee Orientation Guide"
5. Create Your Content Using the Formatting Tools
The rich text editor provides a range of formatting options to help you produce structured, professional documents:
Headings:
Use heading levels to create a clear hierarchy in your document. Main sections get a top-level heading, subsections get lower-level headings. This makes long documents easy to scan and navigate.
Lists:
Bulleted lists - for grouped items, requirements, or information where order doesn't matter
Numbered lists - for step-by-step instructions where sequence matters
Text Formatting:
Bold - for key terms, field names, and important callouts
Italic - for emphasis and references
Underline - for additional highlighting
Highlight - to draw attention to critical information like warnings or deadlines
Multimedia Embedding:
Images - insert screenshots, diagrams, or photos to support written instructions
GIFs - useful for showing a short sequence of actions or a process in motion
YouTube Videos - embed training videos or walkthroughs directly into the document so team members don't have to leave Structur to watch them
Best Practices
Write SOPs in numbered steps - Any document that describes a process your team needs to follow should use numbered lists, not prose paragraphs. Numbered steps are faster to follow, easier to check off mentally, and harder to skip accidentally.
Use headings to break up long documents - A document with ten sections and no headings is exhausting to read. Structure every rich text page with headings so team members can navigate directly to the section they need.
Keep titles specific and searchable - "Onboarding" is a poor title. "New Hire Onboarding Checklist - Field Staff" is a good one. Specific titles make documents findable when your team is searching.
Add images and screenshots wherever a visual makes steps clearer - A screenshot of what a screen looks like at a specific step saves a team member from having to guess. Embed them directly rather than describing the visual in text.
Review and update SOPs when processes change - A document that doesn't reflect how things actually work is worse than no document at all, it actively misleads people. Build a habit of reviewing key SOPs quarterly or whenever a workflow changes.
Organize documents into the right folders and sections from the start - A well-structured Employee Handbook is only useful if documents are easy to find. Put each page in the correct section when you create it rather than leaving cleanup for later.
Common Questions
Q: What types of documents can I create with rich text pages?
A: You can create any type of internal document, standard operating procedures, employee training guides, company policies, project documentation, and knowledge base articles. If it's written content that your team needs to reference, a rich text page is the right format.
Q: Can I embed videos in a rich text page?
A: Yes. The rich text editor supports embedding YouTube videos directly into the page. This is particularly useful for training materials, you can combine written instructions with video walkthroughs so team members have both formats available.
Q: Can I insert images or screenshots?
A: Yes. You can insert images and GIFs into any rich text page. Screenshots are especially useful in process documentation to show exactly what a screen should look like at a given step.
Q: Where do rich text pages live in Structur?
A: Rich text pages are created within the Standard Operating Procedures section of Structur, organized into folders and sections. This keeps all your internal documentation in one place, accessible to your team within the platform they already use daily.
Q: Who can see rich text pages I create?
A: Visibility depends on the role-based permissions configured for your Structur account. If you're creating documents intended for your full team, ensure the relevant users have access to the Standard Operating Procedures section. Review permissions in Settings if you need to adjust who can see specific content.
Common Mistakes to Avoid
❌ Don't | ✅ Do |
Write SOPs as unstructured paragraphs | Use numbered lists for any step-by-step process, they're faster to follow and harder to skip |
Use vague titles like "Policy" or "Checklist" | Write specific, searchable titles that describe exactly what the document covers |
Create rich text pages without headings | Use heading levels to create clear sections, especially in longer documents |
Skip adding visuals to process documentation | Embed screenshots and images wherever a visual makes a step easier to understand than text alone |
Leave documents in the wrong section or folder | Navigate to the correct section before creating the page so your handbook stays organized |
Create an SOP and never update it | Review and update process documents whenever your workflows change so they stay accurate |