Contact us

Virto Portfolio capabilities and limits

Virto Portfolio is a project portfolio and resource management app for SharePoint Online, with the same portfolio in Microsoft Teams, Outlook, the Microsoft 365 app and a browser tab. It plans projects by program, staffs their roles with resources and shows who is overbooked. The app is made by VirtoSoftware, which has built apps for SharePoint and Microsoft 365 since 2011.

Where it runs

  • SharePoint Online: a web part on a page. It shows the portfolio of its own site or of another site chosen in its settings, and can be shown to a chosen audience only.
  • Microsoft Teams: a tab in a standard, private or shared channel, a group chat or a meeting, and a personal app.
  • Outlook and the Microsoft 365 app: the personal app, once the app is installed in Teams.
  • A browser tab: the same screens at portfolio.virtosoftware.com.
  • Outside SharePoint, a Welcome screen lists the portfolios you can open, and Switch portfolio moves to another one.
  • It follows the theme of the SharePoint site and the light, dark or high-contrast theme of Teams and Outlook. The interface is in English.

See Installation and setup.

What it does

  • Projects grouped by program, with a type, a status and a priority in color, dates, managers, a description, planned and assigned hours, and a budget.
  • Gantt chart of programs, projects, roles and assignments by weeks, months or quarters, with milestones, a line for today, a card for each bar and a date range to show. Bars are moved and resized by dragging, several at once with Ctrl+click, and the last 20 changes on the chart can be undone.
  • Roles and assignments: the roles a project needs with their planned hours, skills and planned cost, and the resources assigned to them with a period and an FTE share. Resources are offered by how many of the role’s skills they have. Assignment hours are counted from the resource’s working calendar, and a default constraint (Date, Work or FTE) decides what follows when dates, hours or FTE change.
  • Costs: resources have a cost per hour in their own currency; an assignment keeps its cost in the base currency at the rate of the day it was made. The project shows planned and assigned hours and the budget.
  • Milestones: a start, a finish or a range.
  • Move a project by working days with its roles, assignments and milestones, with a preview before it is applied.
  • Resources: people from Microsoft 365 with their profile photos, contractors and vacancies, with role, department, location, skills, calendar, availability, cost per hour and days off.
  • Load: each resource’s assigned hours against the hours it can work, by weeks or months, with overbooked periods in red, and the projects behind a period shown in Projects or on the Gantt chart. The same by role: the hours projects plan for a role against the hours of the people with that role.
  • Working calendars: hours per weekday, public holidays of 36 countries computed for any year, and days off of the calendar and of each resource.
  • Excel: export of the whole portfolio, and import of projects, plans, milestones, resources, calendars and dictionaries with a preview and a check of the file before anything is written. A demo portfolio for a first look.
  • Dictionaries and settings: programs that can be switched active or inactive with their projects, currencies with rates, departments, roles, locations, skills, unit types, project types, statuses and priorities that can differ by project type, the date format, and whether FTE and budgets are shown.
  • Permissions: the members of the Portfolio Owners and Portfolio Managers groups are managed in the app.

What it does not do

  • No tasks, dependencies or timesheets. Work is planned as roles and assignments of a project, in hours.
  • One portfolio per SharePoint site. Several portfolios are kept on several sites; a web part or a Teams tab can show the portfolio of any of them.
  • Public holidays are national holidays of 36 countries. For other countries and for regional holidays, add the days off to a calendar by hand.
  • Outside SharePoint, the app needs an administrator’s approval for the organization, because it asks for full control of SharePoint sites. The web part in SharePoint does not.
  • No access for people from another organization in a shared channel without a guest account (B2B direct connect).
  • SharePoint Online only, not SharePoint Server, and no native mobile app.
  • English only. The screens are in English, and the setup names the lists in English whatever the language of the site.

Requirements

  • SharePoint Online in Microsoft 365, and a site for the portfolio.
  • A SharePoint Administrator who adds the app from the SharePoint Store. The web part needs no Microsoft Entra app of its own; for profile photos, a Global Administrator approves the Microsoft Graph permission User.ReadBasic.All in the SharePoint admin center.
  • A site owner who runs the setup once.
  • For Teams, Outlook, the Microsoft 365 app and the browser tab: a Teams Administrator who makes the app available, and a Global, Cloud Application or Application Administrator (not a SharePoint or Teams Administrator) who approves the Microsoft Entra app Virto Portfolio App once for the organization, with the delegated permissions AllSites.FullControl (SharePoint), User.Read and User.ReadBasic.All (Microsoft Graph). See Permissions and data.
  • A license for the SharePoint domain, counted by active resources. When it ends, the portfolio becomes read-only. See License.

Where your data stays

  • All projects, resources, calendars and dictionaries are SharePoint lists on your portfolio site. Excel export and import run in your browser.
  • Virto’s server keeps, for each portfolio site, its address, its settings, the version of the lists and the IDs of the two groups. It also serves the app’s scripts, checks the license and computes public holidays. No list items are sent to it. The server runs in Microsoft Azure in the West US region (United States).
Updated on November 18, 2026