The New SWOOP Private Preview

Customer Admin FAQ

1. Who will have access during the Private Preview?
Initial access will be limited to nominated SWOOP Administrators only. Broader user access is not part of the initial private preview phase and will be considered as part of later rollout planning.

2. Will the new SWOOP replace SWOOP “Classic” during the Private Preview?
No. SWOOP “Classic” will remain available and unchanged during the private preview. Administrators can continue using Classic while evaluating the new version of SWOOP.

3. What has changed compared with SWOOP Classic?
The new SWOOP platform introduces a new user experience and a modernised application interface. The current planning position is that the core customer data and analytics processing remain aligned with the existing SWOOP platform, with the new SWOOP adding a new front-end experience and supporting application layer.

4. Why is this a new app rather than an update to the current SWOOP app?
The new SWOOP has been created as a separate app because it is designed to bring together data and experiences from more than one SWOOP product. Keeping it as a new app allows SWOOP to introduce this broader, cross-product experience without changing the existing SWOOP Classic app during the private preview.

5. Does the new SWOOP access any new customer data?
The private preview uses the same customer data already processed by SWOOP. If your organisation needs a formal confirmation for security review, SWOOP can provide supporting information through the approval process.

6. Is customer data stored or processed differently?
No. Customer data continues to be processed through SWOOP’s existing services and infrastructure. The main customer-facing change is the new SWOOP experience.

7. Do we need to involve IT to get the new SWOOP set up?
SWOOP can provide supporting information for internal approval, including high-level details about the preview scope, administrator-only access, relationship to SWOOP Classic, and answers to customer-specific IT or security questions where required.

8. How long does it take to set up the new SWOOP app?
For most customers using the multitenant app, setup should take less than 10 minutes. This applies when the customer is using SharePoint, or SharePoint and Viva Engage. For single tenant setup where the customer is using Viva Engage only, setup typically takes around 30 minutes to 1 hour.

9. What are you looking for feedback on?
We are especially interested in feedback from administrators on whether the new SWOOP is clear, usable and reliable enough for broader rollout.

Navigation and ease of use
Admin workflows and setup experience
Reporting consistency with SWOOP Classic
Bugs or unexpected behaviour
Missing or confusing functionality
Suggestions that would improve the customer experience

10. Are there any pricing or contract changes for the Private Preview?
No. Participation in the private preview does not change your existing SWOOP pricing, commercial terms or contract. The private preview is being provided so nominated administrators can evaluate the new SWOOP experience and provide feedback before broader rollout.

11. How do I provide feedback?
Feedback should be provided directly through the agreed SWOOP feedback/support channel for the private preview. The product team is also working towards making feedback easy to submit from within the new SWOOP so administrators can raise issues without leaving the page they are using.

12. What happens if I find a bug?
Please report it as part of the private preview feedback process. Finding and resolving issues before broader rollout is one of the main reasons for running a controlled private preview with a small group of administrators.

13. What happens if set up or internal approval takes longer than expected?
That is understood. If an organisation’s internal approval or set up takes longer, SWOOP can continue the discussion and support the approval process. Access can proceed once the organisation is comfortable to continue.

14. Who should I contact if my IT or Security team has questions?
Contact your usual SWOOP representative or the private preview contact provided in the invitation. They can route technical, access, security or approval questions to the right SWOOP team member.

Questions Your Security Team May Ask

Context: The new SWOOP is being made available to a small number of nominated SWOOP Administrators as part of a controlled private preview. The preview is intended to validate the new administrator experience, collect feedback and identify issues before broader release.

Suggested response

What is the new SWOOP?

The new SWOOP is the next-generation SWOOP application experience. For the private preview, it is being provided to nominated SWOOP Administrators so they can evaluate the new interface and provide feedback before broader rollout.

Is this a new vendor or a completely new platform?

No. The new SWOOP is part of the SWOOP product ecosystem. It introduces a new application experience while continuing to rely on SWOOP’s existing processes for data collection, data processing and handling as well as commercial clauses.

Who will have access?

Initial access is limited to nominated SWOOP Administrators only. End-user access is not part of the initial private preview scope.

Will SWOOP Classic remain available?

Yes. SWOOP Classic remains available during the private preview. Access to the new SWOOP does not remove or replace existing Classic access during this phase.

Does The new SWOOP require additional customer data?

No. The private preview uses the same customer data already processed for SWOOP Classic. If a formal approval response is required, SWOOP can provide the appropriate customer-specific security information.

Does The new SWOOP change how customer data is processed?

The new SWOOP uses existing SWOOP data and analytics foundations, with a new front-end experience and supporting application layer. Final customer-facing statements should be checked against the approved security/architecture documentation before sending.

Where is the application hosted?

Customer Instance data is located in the region which was selected for the original SWOOP install, oneSWOOP only data such as user templates and config will also be stored in the customers region which matches their classic swoop set-up.

Access to the app is by a single global entry point on azure using Microsoft Front Door.

Dr.SWOOP Functionality

Same permissions carry over from classic SWOOP.

Does this change authentication or user access?

Authentication is the same (e.g. remains at the customers tenant) - the method is now using MSAL as the front end application is built in React.

Has security testing been completed?

Yes. The new SWOOP has been independently penetration tested prior to the Private Preview release.

Any findings identified during testing have been assessed and remediated in line with SWOOP's security processes. The platform is being made available to private preview customers following completion of these security validation activities.

Additional security information can be provided to authorised customer security teams where required.

How should security concerns or questionnaire requests be handled?

Route any IT/security questions or questionnaire requests to the SWOOP private preview contact. SWOOP can provide supporting information and respond to customer-specific approval questions as needed.

What if the organisation cannot approve access in time?

Participation can proceed once internal approval is complete. If approval takes longer, SWOOP can continue to support the security review and determine the best onboarding timing with the customer administrator.

Note that the longer the approval process takes, the shorter the window for providing feedback will be.

Are there new Microsoft/Azure permissions required?

Yes, please see the table in labeled “Graph API Permissions Requirements” The new App Registration has additional simple requirements for Graph API the permissions required are:

Permission	API	Type	Why it's needed
User.Read	Microsoft Graph	Delegated	Sign in the user and read their own basic profile (name, email).
User.ReadBasic.All	Microsoft Graph	Delegated	Look up other users' names in the organization for search/filtering features (e.g. selecting people in reports).
openid	Microsoft Graph	Delegated	Standard sign-in permission required for Microsoft login.
profile	Microsoft Graph	Delegated	Standard sign-in permission to read the user's basic profile info.
offline_access	Microsoft Graph	Delegated	Keep the user signed in without requiring them to log in again every hour.
user_impersonation	Viva Engage (Yammer)	Delegated	Allow OneSWOOP to retrieve the signed-in user's Viva Engage/Yammer data on their behalf for analytics widgets.
access (app's own custom scope)	OneSWOOP application	Delegated	Lets the OneSWOOP backend securely act on the signed-in user's behalf when talking to Viva Engage — required for the sign-in flow to work correctly.