Installation guide
Upgrade

Move from a manifest upload to the Teams store version.

If you deployed Republic by uploading a manifest package as a custom app, the store listing is now the better way to run it. This is how you switch — including what happens to everyone's history.

Download the PDF guideJump to the steps
~20 minof admin work
Nothinglost from user history
24 hrsfor policies to propagate
Why switch

Four reasons the store version is less work.

None of this changes what Republic does. It changes how much of your time it costs to keep running.

It updates itself

A custom upload stays on whichever version an administrator last uploaded. The store version picks up new releases automatically.

Less to maintain

No re-uploading a zip every time we ship, and no risk of different parts of the business drifting onto different versions.

Easier to verify

The listing shows publisher, permissions and supported clients in one place — usually exactly what a security review asks for.

Self-serve where you want it

Tenants that allow user installs can let people add Republic themselves rather than waiting on a policy change.

The question everyone asks

Does anyone lose their progress?

Carries over

Everything that matters

Republic identifies people by their work email address, not by which copy of the app they're using.

  • Behavioural risk scores
  • Assessment history and streaks
  • Phishing simulation results
  • Reporting history and Virtucoin
One thing resets

The proactive chat link

Republic stores a per-user conversation reference so it can start chats rather than wait to be opened. That reference is re-established the first time each person interacts with the new app.

What to do about it: in your launch note, ask people to open Republic once after the switch. Until they do, that individual may not receive a nudge.

Before you begin

  • A Teams Administrator or Global Administrator account for your Microsoft 365 tenant.
  • A pilot user — ideally an administrator — to verify the switch before everyone else gets it.
  • A maintenance window if you turn out to be on Path A below, where the app is briefly absent for users.
  • The current app package kept to hand for rollback: republic-teams-app.zip.
Before you start

Work out which path you're on

The order of operations depends on one thing: whether the store listing carries the same app ID as the package you uploaded. Establish that first — it decides everything that follows.

1

Record what you have now

In the Teams admin centre, go to Teams apps → Manage apps and filter by Custom apps. Find your Republic entry and note its name, version and app ID. The package published alongside this guide is app ID 1f518d36-07de-4ce5-860c-cc774c7bf327 at version 2.1.0.

admin.teams.microsoft.com
2

Look up the store listing

Still in Manage apps, search the Microsoft apps catalogue for Republic. Open the listing and note its app ID.

3

Note which policies reference the app

Under Teams apps → Setup policies, check which policies list your custom Republic app under Installed apps or Pinned apps. You'll be repointing these.

4

Compare the two IDs

Same ID means the store listing is the same application — Teams won't let both exist, so you follow Path A. Different IDs mean they're separate applications that can briefly coexist, which is Path B and lower risk.

Not sure which you're looking at? Ask your Recyber onboarding contact before you change anything. Getting this wrong doesn't lose data, but it can leave your people without the app for longer than necessary.

Ask us
Migration

Pick your path and work down it.

Both end in the same place. Path B lets you verify before removing anything, so take it if the app IDs differ.

Path A · same app ID

Replace the custom upload

The store listing is the same application as your upload, so there's nothing to run in parallel. Do this outside working hours if you can — there's a short window where the app is absent for users.

1

Remove the custom app package

In Manage apps, filter by Custom apps, select your Republic entry and delete it. This removes the uploaded package from your catalogue; it does not delete anything in Republic itself.

2

Add the store listing

Search the Microsoft apps catalogue for Republic, open the listing and set its status to Allowed.

3

Repoint your setup policies

Open each policy you noted earlier. Remove the old entry if it's still listed, then add the store app under Installed apps and Pinned apps. Save.

4

Verify with your pilot user

Ask them to sign out of Teams and back in, open Republic, and send it a message. They should see their existing history and score — not a fresh start.

5

Tell everyone else

Once the pilot checks out, let staff know Republic has moved to the Teams store and ask them to open it once so proactive nudges resume.

How you know it worked

  • In Manage apps, filtering by Custom apps returns no Republic entry.
  • The store listing shows as Allowed, and appears under Installed apps in each policy you repointed.
  • Your pilot user sees Republic pinned in the Teams sidebar with their history intact.
  • Nobody reports two Republic apps in their sidebar.

If you need to roll back

Keep the app package to hand until the migration is signed off. To revert, re-upload it via Manage apps → Actions → Upload new app, set it to Allowed, and point your setup policies back at it. Because Republic keys everything on email address, rolling back doesn't lose user data either — but don't leave both versions live longer than a verification window, or people will get duplicate messages.

Download republic-teams-app.zip

Troubleshooting

Teams refuses the store app while the custom one is installed

The two share an app ID — you're on Path A. Remove the custom upload first, then add the store listing.

Users see two Republic apps

Expected mid-migration on Path B. It clears once you remove the custom app and the policy change propagates.

A user's history looks empty

Check they signed in with the same work email address as before. Republic matches users on email, so a different address means a different user record. If the address matches, contact your onboarding contact before making further changes.

Proactive nudges have stopped for someone

Their conversation reference hasn't been re-established yet. Ask them to open Republic and send it any message.

The app is still missing after 24 hours

Confirm the user is assigned the policy you edited, and that the app status is Allowed rather than Blocked. Then ask them to sign out of Teams and back in.

Want us on the call?

Your onboarding contact can sit with your administrators while you make the switch.

Get in touch Back to the installation guide