TimeOpera Setup

Step 1

Create the SharePoint workspace site

Create a dedicated SharePoint site for TimeOpera. This site will host your TimeOpera workspace and application data. TimeOpera will only be granted access to this selected site.

A dedicated site improves ownership, lifecycle management, and auditability.
Use the exact site URL from this workspace site later in the onboarding form.
This is the only SharePoint site TimeOpera will access.

Step 2

Create or identify the notification sender mailbox

Create a dedicated sender mailbox for TimeOpera notifications, such as timeopera@contoso.com. This keeps reminders, approvals, and system messages consistent and recognizable.

Use a mailbox that already exists in the customer tenant before onboarding starts.
A shared mailbox is the simplest option for most Microsoft 365 administrators.
You will enter this address in the onboarding form below.

Step 3

Grant backend access to the selected site only

Grant TimeOpera.API access only to the SharePoint site created for TimeOpera. This backend grant is used for validation and provisioning, and is separate from the SPFx API approval in the next step.

Approve access only for the dedicated TimeOpera site, not the wider tenant.
The site URL entered in the onboarding form must exactly match the site that received the grant.
Provisioning will not begin until Microsoft 365 consent and this exact site grant are validated successfully.

Important: Complete the site-specific grant before selecting Connect Microsoft 365. If Microsoft 365 consent was just approved, allow a short propagation window before retrying setup.

Advanced: Site-specific access grant Technical guidance for administrators who want the exact permission model, application ID, and scripted grant options.

Show details

TimeOpera uses a site-scoped SharePoint permission model. Administrators who prefer technical terminology can treat this as a Sites.Selected style grant and, for the current provisioning flow, assign the site role required for provisioning.

TimeOpera application ID 4518948c-51ed-4c53-9835-da3dcc861377

PnP PowerShell Recommended

This is the most direct scripted option for SharePoint administrators.

Install-Module PnP.PowerShell -Scope CurrentUser
Connect-PnPOnline -Url "https://<tenant>-admin.sharepoint.com" -Interactive
Grant-PnPEntraIDAppSitePermission `
  -AppId "4518948c-51ed-4c53-9835-da3dcc861377" `
  -DisplayName "TimeOpera" `
  -Permissions FullControl `
  -Site "https://<tenant>.sharepoint.com/sites/<site-name>"
Get-PnPEntraIDAppSitePermission -Site "https://<tenant>.sharepoint.com/sites/<site-name>"

Connect-PnPOnline Grant-PnPEntraIDAppSitePermission Get-PnPEntraIDAppSitePermission

Microsoft Graph PowerShell

Suitable for teams already using Microsoft Graph PowerShell automation.

Import-Module Microsoft.Graph.Sites
$params = @{
  roles = @("fullcontrol")
  grantedToIdentities = @(
    @{
      application = @{
        id = "4518948c-51ed-4c53-9835-da3dcc861377"
        displayName = "TimeOpera"
      }
    }
  )
}
New-MgSitePermission -SiteId $siteId -BodyParameter $params

New-MgSitePermission Create permission API

Microsoft Graph REST / Graph Explorer

Best for advanced administrators or internal platform teams using direct API workflows.

POST https://graph.microsoft.com/v1.0/sites/{siteId}/permissions
Content-Type: application/json

{
  "roles": ["fullcontrol"],
  "grantedToIdentities": [{
    "application": {
      "id": "4518948c-51ed-4c53-9835-da3dcc861377",
      "displayName": "TimeOpera"
    }
  }]
}

Create permission API Selected permissions overview

Step 4

Upload the TimeOpera package and approve SPFx API access

Upload the TimeOpera package to your SharePoint App Catalog and approve the pending TimeOpera API access request. This approval lets the SharePoint web part request a token for TimeOpera.Api.

Package name: time-opera.sppkg.
This step requires an administrator who can upload SharePoint Framework solutions to the SharePoint App Catalog.
The pending API request should show resource TimeOpera.Api and scope access_as_user.
If SharePoint says the requested permission is not valid, reject the request and use the latest package before continuing.

Admin capability required

Upload solutions to the SharePoint App Catalog
Deploy the solution for the organization
Approve API access requests in SharePoint Admin Center

Practical sequence

Download time-opera.sppkg
Upload it to the App Catalog
Approve the pending TimeOpera.Api / access_as_user request

Approval troubleshooting

Do not continue if the pending request shows a different scope.
Reject invalid requests before uploading a corrected package.
Backend site access from Step 3 is still required for provisioning.

Set up TimeOpera in one controlled flow

Designed for controlled enterprise deployment

Complete setup in this order

Create the SharePoint workspace site

Create or identify the notification sender mailbox

Grant backend access to the selected site only

Upload the TimeOpera package and approve SPFx API access

Complete onboarding and start secure setup

Share the TimeOpera page with the right audience

Teams Setup - TimeOpera Quick Setup Guide