Permissions and data
Where the data is
In your Microsoft 365 tenant. Programs, projects, roles, assignments, milestones, resources and their days off, calendars and all other dictionaries are items of 18 SharePoint lists on the portfolio site. The app reads and writes them from your browser, in your name and with your own SharePoint permissions. Deleted items go to the site recycle bin. Excel export and import also run in your browser: the workbook is not sent to Virto’s server.
On Virto’s server (portfolio.virtosoftware.com), for each portfolio site:
- the address of the site and the ID of your Microsoft 365 tenant;
- the settings: the base currency, which calendar is the default one, the date format, the default constraint, and whether FTE and budgets are shown;
- the version of the portfolio’s lists and the IDs of its two SharePoint groups;
- the sign-in name of the person who last saved these settings, and when.
For each person who opens What’s new, the server also keeps the ID of their tenant and of their account with the time they last read the news. All of this is kept in Microsoft Azure Table Storage. No projects, resources, costs or other list items are sent to the server. The server is a Microsoft Azure App Service in the West US region (United States).
The server also:
- serves the app itself: the scripts of the SharePoint web part and the page that opens in Teams, Outlook, the Microsoft 365 app and a browser tab;
- checks who you are whenever the app reads or saves the settings: it asks SharePoint about the sign-in token the app sends. It does not store the token;
- checks the license of your SharePoint domain with the Virto license server, sending the domain and the sign-in name, e-mail address and name of the person who opened the app;
- counts public holidays: the app asks it for the holidays of a country in a year;
- lists the sites with a portfolio for the configuration page of a Teams tab, the Welcome screen, Switch portfolio and the Portfolio site setting of the web part, checking each one with your own sign-in, so it never names a site you cannot open;
- sends your feedback from Send feedback to VirtoSoftware support by e-mail, with your name and e-mail address for the reply, the address of the site and the ID of your tenant.
Permissions
In SharePoint
In SharePoint the app needs no Microsoft Entra app of its own. The web part works on the page with the SharePoint permissions of the person who opens it, as any other part of the site does.
The package asks for one API permission, approved in SharePoint admin center → Advanced → API access by a Global Administrator, as Microsoft requires for Microsoft Graph permissions:
| Permission | What the app uses it for |
|---|---|
| Microsoft Graph: User.ReadBasic.All (delegated) | Show people’s profile photos in the portfolio |
Without it the app works and shows initials instead of photos. As with every SharePoint Framework solution, an approved permission is granted to SharePoint’s own app for SharePoint Framework solutions in your organization. See Manage access to Microsoft Entra ID-secured APIs on Microsoft Learn.
In Teams, Outlook, the Microsoft 365 app and the browser tab
Outside SharePoint the app signs you in with the Microsoft Entra app Virto Portfolio App. It asks for three delegated permissions:
| Permission | What the app uses it for |
|---|---|
| SharePoint: AllSites.FullControl | Read and write the portfolio lists in your name; set up, update and remove the portfolio, and change the members of its groups, when you are allowed to on the site |
| Microsoft Graph: User.Read | Sign you in; in a browser tab opened without a site address, find the root site of your organization from its domain names |
| Microsoft Graph: User.ReadBasic.All | Show people’s profile photos in the portfolio |
AllSites.FullControl needs an administrator’s consent. A Global, Cloud Application or Application Administrator approves the app once for the whole organization, and that one approval covers all three permissions. A SharePoint Administrator or a Teams Administrator cannot give it, and people cannot accept AllSites.FullControl for themselves. Until then, signing in fails and the app shows a link to the approval page for the administrator. See Make the app available and approve it and Grant tenant-wide admin consent to an application on Microsoft Learn.
A delegated permission never gives the app more than the person has: with AllSites.FullControl, the app can do on a site only what the signed-in person may do there. A site owner can set up the portfolio and change its groups; a visitor still only reads. The app asks for full control because SharePoint lets a narrower permission, such as AllSites.Write or AllSites.Manage, neither create groups nor change permissions, even for a site owner.
A guest signs in to the organization that invited them, and needs the approval of that organization, not of their own. People from another organization in a shared channel without a guest account (B2B direct connect) cannot sign in to the portfolio.
Who can do what
The setup gives the portfolio lists permissions of their own, separate from the site. Site owners keep full control.
| Portfolio Owners and site owners | Portfolio Managers | Site members and visitors | |
|---|---|---|---|
| Projects, roles, assignments, milestones | Edit | Edit | View |
| Programs and their Active switch, calendars and their days off, currencies, departments, roles, locations, skills, unit types | Edit | Edit | View |
| Resources and their days off | Edit | View | View |
| Project types, statuses, priorities | Edit | View | View |
| Settings page: general settings, permissions, license | Edit | Not shown | Not shown |
| Manage the members of the two groups | Yes | No | No |
| Export to Excel | Yes | Yes | Yes |
| Import from Excel | Yes | Projects and dictionaries they may edit | No |
Setting up, updating and removing the portfolio need a site owner: a person who can manage the site and its permissions and create groups.
People who are in none of these groups and cannot open the site cannot open the portfolio either. When the license has ended, the portfolio is read-only for everyone; see License.
The lists are ordinary SharePoint lists on the site, so people with the rights above can also see them in Site contents.