Latest News from the Riipen team

What's new in September 2025

Emily avatar
Shared by Emily • October 06, 2025

Enhanced imports

Import functionality has several updates to make imports more functional and flexible across different use cases.

  • Educators can choose whether or not to notify the employer when they are importing a project for a company.
  • Educators can now directly create a match via import for existing companies. Previously this was available only for new companies, and importing to existing companies would create a pending match request.
  • Educators can now add a new admin to a project for an existing company via import. Previously this would cause the import to fail as only the company itself could add new members.
  • A new import type is now available to import match requests in a pending state, for users who have external contacts but still want to finalize the details in Riipen.

All imported projects since Friday Sept 5 will now be visually labelled as such, indicating to any viewer that the user and/or company was added via import. This label can be removed if the end user logs in and accepts their affiliation with the project.

Experience talent pool

Employers can now see a Learners tab on experience pages (if enabled by admins), allowing them to browse and evaluate potential participants more easily. This is helpful when an educator wants the employer to know more about their learners prior to the team assignment.

  • Tab displays up to 10 learners in horizontal card format with filters for categories and keyword search.
  • Employers can access learner profiles by clicking a card.

Experience admin controls: New Learner privacy settings in experience settings > Privacy tab. Options include:

  • No visibility (default)
  • Visible to matched employers
  • Visible to logged-in employers
  • Visible to non-users

Closing experiences to new team formations

Experience administrators can now close an experience to new team formations once project matching is complete or capacity has been reached. Previously, only application-based team creation could be restricted, leaving self-assign and admin-assign methods open.

  • Experience settings: A new control under Participants > Team creation allows admins to set team formation to Open (default) or Closed. This applies across self-assign, admin-assign, and application methods.
  • Admin controls: When closed, experience admins cannot create new teams. Options such as Invite to teams, Create team, or + Teams are disabled, with a yellow notice linking back to team creation settings.
  • Learners: Learners cannot start new projects. For self-assign, the Join project button is removed, and projects display a closed pill on experience and match pages.
  • Match settings: Experience-level closures override match-level settings. Matches can still be closed individually if the experience remains open.
  • Visual indicators: Pills now display Open, Closed, or Open – Invite only (for admin-assign), with tooltips explaining the status of new team formation.

Project extension via change request

Change requests are now available on active, inactive, and incomplete teams and matches.

With the new feature, users can request to change three main things:

  • Dates - extend or shorten the project/team timeline (depending on who the date controller is).
  • Hours - increase or decrease the maximum number of project hours (within the allowed experience range).
  • Content / Scope (only available for team change requests) - add a project addendum explaining why the scope has shifted (e.g., extended timeline, extra tasks, expanded requirements, or a new project addition).

Improvements

  • Match request email improvements: Updated emails now clearly indicate when immediate action is required and provide guidance on managing expiring requests
  • Team submission reminder emails updated. Reminder emails for team submissions (milestones, final deliverables, overdue submissions) were refreshed. Updates include clearer subject lines, simplified copy, and stronger calls to action with direct links to submit or review.
  • Match request “Next steps” improvements. The Next steps section on the match request page now shows actions for both parties. Steps are dynamically ordered depending on who acts first, with completed actions clearly marked and moved above incomplete ones.
  • Employer notice for pending applications. Employers now see a yellow notice in the expiring applications email encouraging them to respond to pending applications.
  • Earlier match expiry reminders. Employers now receive match expiry reminders earlier; expiring requests show 8 days before expiry in digest emails and a standalone reminder email is sent 10 days before expiry.
  • Company details required. When editing a company profile, location, website, and industry fields are now mandatory.
  • Guest project generation for employers. Employers can now generate projects as guests on riipen.com via the ChatGPT Webflow plugin. After signing up, the generated project is saved as a draft and opened in the project wizard to complete setup.
  • Experience setting for certificates. Experience admins can now disable certificates for learners. A new setting under Experience settings > Project management > ‘Learner settings’ controls whether certificates are awarded when teams complete a project. If disabled, certificates are removed from benefits panels on both match and team pages.
  • Portal membership suspension. Portal admins can now suspend or reactivate learners and educator members of their portal from their member pages.
  • Portal resources update. Portal admins now see both Riipen default resources and their portal’s own resources under Portal Content > Resources if Riipen resources are enabled in the portal settings.
  • Education fields updates. Learners can now fill in education information from the onboarding wizard and application wizard. Institution and degree fields are now a searchable dropdown.
  • Learner view > Join experience page. Learners viewing a Join experience page for an experience they are not a member of will now see a notice clarifying that they must be enrolled in the relevant program or course to join, and that they should obtain the access code from their educator or administrator.
  • Payment flow at match request acceptance. Employers are now informed that a temporary authorization hold of $1 will be placed on their card to accept a request for experiences that are paid by the employer in-platform. If authorization fails, an error explains the issue and prompts updating the payment method.
  • Achievement image refresh: Default Riipen achievement images have been updated with more visually engaging designs. This includes variations for achievements with multiple levels or tiers.
  • Updated educator dashboard experience cards. The experience table in the educator dashboard has been updated to use the horizontal card style used in learner dashboards to let educators see more information about each experience at a glance.
  • Work log creation for completed teams. Learners can now log work on teams in the Completed state to allow for cancelled invoices on completed teams to be fixed and manually re-generated.
  • Profile page content reordering. “Latest feedback” section now appears above “Achievements” for all user profiles.
  • Search experience matches by skill. Learners can now search experience matches by skill to better find relevant opportunities.
  • Claiming imported projects as an employer. As an employer, you can now claim a project that was imported for you or your company.
  • Invoicing improvements. The Invoiced column in the work log now updates instantly when an invoice is created, without requiring a page refresh. Experience administrators can now manually create invoices for completed teams, even when auto-generation of invoices is enabled.
  • Survey settings update. A requirements section is available under Survey > Settings, with two configurable options: Is this survey required for project progress? And, Is this survey required for invoices? These settings can be edited after a survey is published and even after responses have been collected.