Sharepoint integration within document management

Multi-language surveys

Surveys are written in one language. To reach people who speak another language, admins duplicate the survey and target each language through the audience. Admins can write one survey in more than one language, the same way as forms and courses. Each survey has a primary language, chosen when it is created. Adding a language translates the whole survey. That translation can be edited. Questions, answer options, slider labels and text blocks are translated. The questions themselves, the audience and the planning stay the same in every language. Someone filling in the survey sees it in their translation language. If that version does not exist, they see their app language, then the primary language. All answers add up in one report, whatever language people answered in. Existing surveys get their primary language from their content. Pulse surveys are not part of this.

Multi-language documents

Documents and pages are in one language. To reach people who speak another language, admins upload or write a separate copy per language, and people have to find their own version. Admins can add more than one language to a document or page, so everyone gets the version in their own language. Files: upload a version of the same file for each language, for example a Dutch and an English handbook. Files are not translated automatically. Pages: adding a language translates the whole page. That translation can be edited. When the primary page changes, the other languages are marked as outdated and can be translated again with one click. Everyone sees a document or page in their own language. If that version does not exist, they see the primary language. AI Buddy and search find documents in every language. Folder names and personal documents are not part of this.

Multi-language performance review forms

Performance review forms will support multiple languages, just like Forms and the Academy. You set up one evaluation form and add the languages your team needs, instead of keeping a separate copy of the form for every language. One form, multiple languages: choose a primary language and add more languages. New languages are translated automatically with AI, and you can review and edit every translation. Everyone in their own language: the employee and their manager(s) each see the same evaluation in their own language while they work on it together. Scores, ratings and the 9-box add up the same way, whatever language someone uses. Translate written answers: when someone writes an answer in another language, you can translate it with one click to read it in your own language. The original answer is always kept. Competencies and rating scales: the competency library, categories and rating scales (including scale descriptions) can be managed in multiple languages. Notifications and exports use the form in each person's language. Review cycle and moment names are not included and stay in the language you write them in.

Multi-language organisation messages

Company updates are written in one language. People who speak another language see that version, unless they tap Show translation on the timeline. Admins can write one company update in more than one language. That includes the text, every attachment, the poll, and the link preview. The first language is the organisation’s default language. Adding a language translates the text. That translation can be edited. Each language can have its own attachments, of any type and any number. A language without its own files uses the original ones. A poll is still one poll. The question and the answers are translated, and votes add up across languages. On the timeline, someone sees the version in their translation language. If that version does not exist, they see their app language when that translation exists, then the organisation’s default language when that translation exists, then the original. Show translation stays on the timeline, and only when the version shown is still not their translation language. The notification uses the same language as the timeline. Likes, comments, and the poll result belong to the one update. Extra languages are added on the web. Creating a company update on mobile still uses one language.

Apply introduction changes to existing employees

Turning off new employee introductions only changes who gets asked from now on. Employees who were invited while the setting was on still see the introduction prompt. What we'll add: The setting still controls whether people invited from now on are asked to introduce themselves. Turning it on does not ask people who are already in the organisation. Turning it off asks whether that applies to new employees only, or also to existing employees who have not introduced themselves yet. Choosing existing employees clears the prompt for those who have not posted an introduction. People who already introduced themselves stay as they are.

Chatbot sources as linking chips

When the AI buddy refers to something in Oneteam, that source is not shown as the same link chip used on messages. What we'll add: Buddy sources rendered as those linking chips, including when a conversation starts

Add internal deep links to all user generated content

What's the request? Internal links already exist in Oneteam: from an item's share option you get a fixed URL to a message, event, form, survey, document, Academy learning or flexchange. In the timeline and chat those links are recognised automatically and shown as a clear label. The request is to make internal links usable in the other places where you write content — Academy courses, event and meeting descriptions, documents — with the same recognition, and ideally with a picker so you can search and insert Oneteam content instead of copying a URL from elsewhere. Concrete examples Linking from an Academy course to an event or timeline post, for example a practical session or important message that goes with the theory. Linking from the description of an in-person training event to the e-learning employees need to complete beforehand. Linking from a scheduled meeting event to the document or message that serves as preparation. What could this look like? The same link recognition that works in the timeline and chat, applied to the editors in Academy, Events and Documents. On top of that, maybe even a link option in the editor that lets you search and select Oneteam content directly, similar to tagging a colleague, so admins don't have to open the item, copy the link and paste it back.

Academy course creation on community level

Currently, only organization admins can create Academy courses. This means community-specific training needs (content that's only relevant to a particular office, location, or team) can't be created and managed by the people closest to that context. Desired solution: The ability for community-level admins/managers to create and manage their own Academy courses, scoped to their community. Current behavior / workaround: Community admins are provided with organisationadmin rights for academy. Impact: Location- or team-specific training (e.g. building safety, office arrival procedures) can't be created by the people who actually own that knowledge Extra dependency on organization admins to create content that isn't organization-wide Slower rollout of relevant, local onboarding and training material

Reply to a comment

You can reply to a comment, and to a reply, on timeline posts, form submissions, and tasks. Replies sit under the comment they belong to, slightly indented, with a smaller profile photo and a line connecting each level. The whole thread is shown. Reply opens the usual comment box, with a header that says who you’re replying to and their name filled in at the start. A reply can include the same things as a comment, such as mentions and attachments. A thread can go four replies deep under the original comment. On that last level, Reply adds another comment on the same level and mentions the person you tapped. The person you reply to is notified.

Attach videos and multiple images to a comment

A comment can only include a single photo. That applies to comments on timeline posts, events, tasks and form submissions. Timeline posts and chat already allow videos and several images together. What we'll add: A video on a comment Several images and videos on one comment, including a mix of both The same attachment grid already used on timeline posts and in chat

Flexible task deadlines

Task deadlines work differently for one-time and recurring tasks, and a recurring deadline can only fall on the same day. A weekly task that opens on Tuesday and should be due on Saturday cannot be set up that way. What we'll add: One deadline setting for both one-time and recurring tasks: same day, next day, or up to 14 days later, plus a time of day The task closes at that deadline if it has not been submitted, and shows as expired A recurring task stays open until its own deadline, even when the next occurrence has already opened

Community properties

Custom properties on community level, mimcking the implementation of custom user properties. These properties can be assigned to a community, and can later be used in the audience selector @Expand the audience selector to filter on groups and results from other modules

Learning path improvements

What we’ll add: Phasing of courses within the learning path based on X days after learning path is assigned to employee Add settings to course to only show the course in a learning path. When enabled, the course won’t be visible in the general course library anymore

Overview or awareness that feedback has been given on a learning

Recently Oneteam added the option for employees to leave feedback after the course is completed. If you have 2 courses, its is manually okay to check if feedback was left behind, however when you have 15 for example it is not. Suggestion would be that in the general statistics there would a way to see new feedback has been added or maybe behind de user add an extra mark regarding ‘feedback ✅’

See if chat message has been delivered & read

Task Management

Introduce multiple like types

Currently, a like is always a high five. Similar to other social platforms, we want to support multiple like types

Allow editing of attachments for timeline messages

An improvement that has been on the roadmap for quite some time. The possibility to change attachments on a (scheduled) timeline / organisation message.

Multilingual support for academy courses

Currently when an organisation has employees that speak multiple languages, they must create separate content for them and target them through the audience selector. We want to simplify this by allowing multilingual support within the content creation, and serving the content based on the users language.

Certification after finishing a course

The ability to download a certificate that a specific employee has completed a course

Add possibility to send organization message from a user instead of organization name

Allow community admins to create events

Currently, the creation of events is only available for organization admins. We will add support for community admins to also create events for their own community with a new unique permission to do so.

Univeral linking between app and dashboard (link / share / url's)

This feature enables seamless sharing and display of internal resources (posts, events, forms, surveys, users, documents, academy courses) across web, mobile, timeline, and chat. It introduces baseline URLs as short links, provides a share modal with QR/copy options, and ensures that shared links are resolved and displayed consistently across platforms.

Add description to organization or community group