Skip to main content
Policies and procedures

Knowledge Base

Policies, procedures, and internal guides in one governed library your L&D team owns: organized into spaces, versioned under named owners, and targeted at the people they apply to. Assign a policy the way you assign training, and Salalem keeps the record of who read and acknowledged which version. Then the assistant answers questions from those same documents, and cites the page it drew the answer from.

The policy, the course that explains it, and the proof it was read — one system.

  • Knowledge Spaces

    Policies, procedures, and guides organized into spaces your team names — HR, IT, Safety — each holding its own entries. Employees browse and read them in the same app they train in, and Arabic documents render as first-class right-to-left pages.

  • Read and Acknowledge

    People confirm they have read the policy, Salalem reminds whoever has not, and you see who acknowledged which version and when. The acknowledgement can only be given from the last page of the document — a record here means it was read through, not clicked past.

  • Versions and Owners

    Every entry has a named owner and a review date, so nothing goes quietly stale. A new version supersedes the old: search and answers return only the current text, prior versions keep their acknowledgements on file, and you decide whether the new one must be read again.

  • Audience Targeting

    Visibility follows your org structure: a whole space or a single entry goes to the departments, roles, or groups it applies to. Narrowing a space holds for everything inside it, and what someone browses or searches is only ever what they are cleared to read.

  • Courses from your policies

    A code of conduct is often better as a course than a PDF — richer than a document, with an assessment built in to check understanding. Build it from the policy already sitting in your library, review the draft, and it feeds the assistant's answers alongside your documents. Publish a revision later and the course is flagged for review rather than quietly rewritten.

  • Coverage Gaps

    A report of what employees searched for and your sources could not answer, grouped by the words they used, beside the entries nobody has opened at all. It names the policy worth writing next instead of leaving you to guess.

The chain

From the policy to the proof it was understood

  1. The policy

    Published to the departments, roles, and groups it applies to. This is the link the rest hang from: revise the document and everything downstream follows the version you published.

  2. The course that explains it

    A policy states the rule; a course shows how it is applied. Author it in the same platform, assign it to the same audience, and the assistant answers from both.

  3. The assessment that verifies it

    An acknowledgement proves the document was read. An assessment on the same material shows which parts of it landed, while there is still time to fix the gap.

  4. The record

    Who acknowledged which version and when, who completed the course, and what they scored — one history per employee, exportable the day someone asks for it.

The assistant

Answers from your documents, with the page they came from

Employees ask in their own words and get an answer drawn from the documents you approved, written out as it is generated, with a citation that opens the source at the page it came from. Admins choose which spaces it may read, test the answers before publishing, and see the source list it is answering from.

  • Every answer names its source

    The citation beside an answer opens the document at the page the answer came from, so the reader can check the policy itself.

  • It declines rather than guesses

    When the approved sources do not cover a question, the assistant says so and points the employee to the internal owner who can answer it.

  • It answers within each reader's permissions

    A document restricted to one department is only ever cited to that department. The audience you set in the library holds when the assistant answers.

  • Admins decide what it reads

    Its sources are the spaces you switch on, files uploaded to it, and courses you select. A space is never included because its documents were published — an admin turns it on, and can see what is indexed, stale, or excluded.

Knowledge assistant

Ask about any policy

Arabic · English · French
Employee
Can I claim transport home after a late shift?
Assistant

Yes. When a shift ends after 10pm, transport home is reimbursed up to SAR 120 — attach the receipt to your expense claim within 30 days.

Source Travel and Expense Policy v4 · page 7

Answers come only from the spaces an admin switched on.

Packaging

What comes with the platform, and what is priced on top

  • Included in every plan

    The library and read-and-acknowledge tracking come with the platform subscription: spaces, versions, named owners, audiences, and the record of who read what.

  • The assistant is an add-on

    The assistant that answers from those documents, and the coverage reporting behind it, are priced on top. The shape that fits your workforce is worth a conversation rather than a table.

Bring One Requirement. Leave With Its Record.

Give us an hour and one real requirement — from your rulebook or from a role profile. You will see how it maps to people, deadlines, and evidence on Salalem.

Get a Demo
Get a Demo