Portfolio Administration

Administration tasks

The tasks that the Portfolio Administrator can perform are:

  • Install Portfolio

    Check system requirements, download, and install the Portfolio server software. See Software installation.

  • License Portfolio

    Enter credentials for the Portfolio License Administrator. See Licensing Portfolio.

  • Configure extra Media Engines

    A Media Engine is a separate system that can handle the heavy lifting of image cataloging and conversion. See Media Engines.

  • Configure Portfolio backups

    It’s always a good idea to back up your important data. See Backups.

  • Create user accounts

    Add users from your organization to Portfolio so they can access assets. See Adding user accounts.

  • Create catalogs

    A catalog is where Portfolio stores your assets. You can create different catalogs for different uses. See Portfolio catalogs.

  • Refine user roles

    Portfolio initially has four predefined user roles. You can change these, or create more roles to fit your users’ workflows. See Roles.

  • Change server data locations

    Portfolio has several data locations. You can move them depending on your organization’s storage needs. See Server data locations.

  • Configure directory services

    You can let users log in to Portfolio using their network credentials. See Configuring Active Directory and Mapping users from Active Directory.

  • Customize Portfolio Web login screen

    You can brand the Portfolio Web client for your organization. See Portfolio Web login customization.

  • Configure mobile upload

    Users can upload images as assets from their iOS or Android device. See Mobile uploading.

  • Configure Single Sign-On

    If your organization uses a directory service, you can also configure user accounts to connect using the credentials they use to sign in to their computer. See Configuring Single Sign-on.

  • Configure email notifications

    Portfolio can send email notification for various events. See Email notifications.

  • Configure SSL

    You can configure Portfolio to use a signed SSL certificate. See Adding SSL for secure connections.

  • Change ports used by Portfolio

    Portfolio uses several communication ports. While the default ports aren’t commonly used by other applications, you can change them if there is a conflict. See Ports.

Portfolio adds the Portfolio Administrator to every catalog with the role of Catalog Administrator. See Catalog administration tasks for other tasks associated with that role.