Build an employee training portal with SmartSuite and Softr

Executive overview

Every time a new team member joins, existing staff lose productive time re-teaching the same fundamentals. The solution is a one-time build: a structured training library in SmartSuite backed by relational tables for resources, courses, and employees, then surfaced through a Softr interface that gives staff and managers a polished online-course experience. SmartSuite holds the data and logic; Softr handles login, permissions, and a consumer-grade UI — each tool free-tier eligible. Managers get a separate view showing direct-report progress; employees see only their own assigned courses.

Build your training library once in a proper relational database and wrap it in a no-code portal so onboarding scales without stealing time from your team.

Setting up the SmartSuite training library

• Start from SmartSuite's built-in employee learning template to save 20–30 minutes of manual setup.
• Three core tables: Resource Library (content items), Courses (grouped learning paths), and Employees (humans and their progress).
• Linked record fields connect tables relationally — a course links to its resources and to the employees enrolled in it.
• Use SmartSuite's data schema widget (dashboard view) to visualise how tables connect before making changes.
• Rename default linked fields to plain-English names (e.g. "My Courses", "My Learning Tracks") for clarity.

Customising the employee table for progress tracking

• Add a linked record field called "Manager" that points back to the same Employees table; restrict to one entry and require a value.
• Duplicate the "My Courses" linked field to create a second field, "Courses Complete", so enrolled vs. finished courses are tracked separately.
• Add a formula field "Courses Remaining" using COUNT(My Courses) - COUNT(Courses Complete) to report outstanding work at a glance.
• These three additions — manager link, completion field, remaining count — are the minimum needed to drive manager dashboards in Softr later.

Filling the training library with content

• Three sourcing strategies: buy external courses (e.g. LinkedIn Learning), observe yourself training a new hire and have them capture notes, or borrow from others' libraries.
• Recommended resources to include: core values document, what-you-sell overview, customer avatars, brand/voice guide, meeting and communication norms, software how-to courses, time-off submission SOP, workspace tour video, company origin story, HR handbook, and role-specific SOP collections.
• The "observe yourself" approach doubles as live onboarding and SOP capture simultaneously.
• Role-specific SOP bundles are best added per-hire rather than kept in the general library.

Connecting Softr to SmartSuite

• In Softr, create a blank application and keep the default pages: home, list, detail, login, and a blank page; uncheck sign-up form and user profile at creation.
• Add SmartSuite as a data source under a List page's dynamic block; select the Courses table to power the course library page.
• Sync Softr's user system with the SmartSuite Employees table (Users tab → Sync with data source), mapping email, name, and photo fields.
• After syncing, all employees appear as Softr users; changes flow both ways — adding a user in Softr creates a record in SmartSuite.

Setting up user groups and permission layers

• Create two Softr user groups: "Managers" (Title field = Manager) and "Employees" (Title field is not Manager).
• Visibility rules on navigation bars control what each group sees — employees get a standard nav, managers get an additional "My Direct Reports" tab.
• Filter the course list page so each logged-in user sees only courses linked to their employee record in SmartSuite.
• Managers' direct-reports page shows progress data and exposes actions: add a direct report, update employee info, download a report — all of which write back to SmartSuite.

The finished portal and next steps

• The working portal gives employees a branded login page, a personal course list, and a detail page that can embed video and rich content from SmartSuite fields.
• Managers see team progress and can update records without ever touching SmartSuite directly.
• SmartSuite remains the single source of truth; Softr is purely the interface and permission layer.
• Beautification (custom domain, app icon, branded colours) can be layered on after the functional build is complete.
• Recommended progression: start by writing down training as you do it → consolidate into SmartSuite → build the Softr portal → then polish the UI.