HELP FILE

Push Sites to Users

LastPass Enterprise admins can use Push Sites to Users to directly place a Site in a user’s Vault. This can be used to pre-populate a Site in a user's Vault so that it is available when the user first logs in, and to push SAML-specific URLs to services you have linked to your account when using LastPass Single Sign-On.

Another unique aspect of Pushed Sites is that due to how the technology behind pushing Sites works, any data you elect to push to your users is accessible on LastPass servers in unencrypted form until the data is pushed to a user. Once pushed to a user, the data will leave the LastPass server and be encrypted in the user’s individual vault. This is not the case with Persistent Pushes, which will stay on the LastPass server until deactivated or deleted.

Please note that the user receiving the pushed Site must log in using the LastPass web browser extension at least once to receive it. If the user logs in via the LastPass website, the Site will not be pushed.

Topics in this article:

About Push Sites to Users

Push Sites using a CSV upload

Manually fill in fields to push Sites

Persistent Site pushes

Previously pushed Sites

About Push Sites to Users

The following considerations should be noted before using Push Sites to Users:

  • Once the Site is received by the user, the admin cannot remove the Site from the user's Vault.
  • Data you elect to push to your individual users is accessible on LastPass servers in unencrypted form until the data is pushed to a user. Once pushed, the data will leave LastPass servers and become encrypted in the user's Vault.
  • The data in Persistent Site pushes remains stored on LastPass servers in unencrypted form until the data is pushed to new users that are added to groups or your Enterprise. However, the data will remain on LastPass servers as unencrypted (as it waits to be pushed) unless the Persistent Site is manually deactivated or deleted. Learn more below.

Push Sites using a CSV upload

You can download our sample CSV file, or create your own spreadsheet that matches the title columns and format in our sample file.

You can also add custom fields to your CSV in the following format:

fieldname0,fieldtype0,fieldvalue0,fieldname1,fieldtype1,fieldvalue1

The following is an example using the custom field format:

usernamefield,text,newuser,pwfield,password,abc123

Which yields a text field with the name usernamefield and the value newuser, and a password field with the name pwfield and the value abc123.

  1. Go to https://lastpass.com/company/#!/dashboard and log in to access the Admin Console.
  2. Go to Advanced OptionsPush sites to users.
  3. Click Choose File, then select your file and click Open.
  4. Click Push Site at the bottom of the page.

For your users to receive the pushed Site, they must log out after the Site is pushed and log back in to LastPass using the web browser extension.

Manually fill in fields to push Sites

You can fill in all of the require fields to push Sites, as follows:

  1. Go to https://lastpass.com/company/#!/dashboard and log in to access the Admin Console.
  2. Go to Advanced OptionsPush sites to users.
  3. Fill in the following required fields:
    • User(s) – Use the drop-down menu to select the user or user groups to which you'd like to push the Site. Alternatively, you can select All Users to push to all current and future users in the Enterprise, or all current and future members of a user group. Note: When a Group or All Users is selected, you have the option of enabling the Site as a persistent push. Learn more below.
    • URL – The URL of the Site entry that you’d like to push
    • Name – The name you would like the Site entry to have in the users’ Vaults
    • Folder – The name of the folder you’d like this Site to be added under in the users’ Vaults
    • Username – The username the users will utilize to log in to the Site. You can select to have this be the individual’s full email address that is used as their LastPass account name (only the username portion of the email address), or a custom username you manually enter
    • Password – The password that will be used to log in to the individual Site
    • Notes – Any notes that you would like to be entered into the notes portion of the Site entry
    • Favorite – Check the box to allow this Site to be marked as a Favorite in users’ Vaults
  4. When finished, click Push Site.

For your users to receive the pushed Site, they must log out after the Site is pushed and log back in to LastPass using the web browser extension.

Persistent Site pushes

A Persistent Site push is an optional setting you have when you have elected to push a Site to a group of users or all users within your Enterprise (not individual users). LastPass will keep this Site information on our servers (unencrypted) and push the Site to any new users that are added when you select a Group or All Users as they get added to your Enterprise. Once the users log in via the LastPass web browser extension to receive the Site, the data becomes encrypted in their Vault.

Previously pushed Sites

You can view all previously pushed Sites and detailed information about each, and choose to deactivate or delete a Persistent Site.

  1. From the Admin Console, go to Advanced OptionsPush sites to users.
  2. At the top of the page, click the hyperlink Click here to view a log of previously pushed sites.
  3. Displayed on the page is the name of the pushed Site, list of users or user groups it was pushed to, whether the push was persistent, and whether or not the push is still active. Additionally, you can take the following actions:
    • Details – Displays the individual users that had the Site pushed to them.
    • Deactivate – Prevents persistent pushes from being pushed to new users. This effectively turns the persistent push “off.” Sites can be re-activated at a later time to be “re-pushed” to any new users that have been added since the push was deactivated.
    • Delete – This permanently deletes the pushed Site from the system. Please note, this will not remove the Site entry from the individuals’ Vaults, but only the push from the LastPass servers.