Salesforce1 Admin Rollout Guide ›

1. Set-up the App for Your Users

Get the App

 

 Download the App:

You can get Salesforce1 in different ways:

  • As a downloadable app from the App Store and Google Play™. Users can install it directly on iOS and Android mobile devices.
  • As a mobile browser app that runs in supported mobile browsers on Android, iOS, BlackBerry, and Windows 8.1 (Beta) mobile devices. This option doesn't require anything to be installed.

 

 

Supported Browsers and Devices for the Mobile Browser App:

You can access the Salesforce1 mobile browser app in these environments.

  • Apple Safari® browser on iPad® 2 and later models (including the iPad mini) and iPhone® 4 and later models, with iOS 7 or later
  • BlackBerry® Browser on BlackBerry Z10 devices with BlackBerry OS 10.2 or later and BlackBerry Z30 devices with BlackBerry OS 10.2.1.3175 or later. (Salesforce1 isn't supported on BlackBerry Q10 devices.)
  • Google Chrome browser on Android phones with Android 4.2 or later.
  • Good Access™ secure mobile browser on Android™ phones with Android 4.2 or later and on Apple® mobile devices with iOS 7 or later.
  • Beta version: Microsoft® Internet Explorer® 11 browser on Nokia™ Lumia™ 1020 and HTC™ 8X phones with Windows® 8.1. (Salesforce1 isn't supported on mobile phones with Windows 8.0 or on Windows tablets.)

 

 

Salesforce Editions and Licenses:

These Salesforce editions allow the use of Salesforce1.   A special Salesforce1 or mobile license isn't required.

  • Contact Manager Edition
  • Developer Edition
  • Enterprise Edition
  • Group Edition
  • Performance Edition
  • Personal Edition
  • Professional Edition
  • Unlimited Edition
  • Database.com edition isn't supported.

These user license types can access Salesforce1

  • Salesforce users
  • Salesforce
  • Platform and Force.com users
  • Chatter Plus users, Chatter Free users, and Chatter customers
  • Customer Community and Partner Community external users
  • Portal users who are a member of a Salesforce community

These user license types aren't supported: Portal users (unless a member of a Salesforce community), Database.com users, Sites and Site.com users, Data.com users, and Work.com users.

Enable Salesforce1 for Your Org

The Salesforce1 Mobile App is automatically enabled for all existing and new instances of Salesforce, except those for which auto-enablement is specifically turned off.   To turn on Salesforce1 - there are a few simple steps:

 

 

1. Set Your Connected Apps Permissions

You'll want to make sure Salesforce1 is turned on for your org by navigating to Setup → Manage Apps → Connected Apps and configuring settings for "Salesforce1 for iOS" and "Salesforce1 for Android."

These components are automatically installed when one of your users downloads the Salesforce1 Mobile App onto their iOS or Android device and logs into Salesforce.

You can also manually install the Salesforce Connected Apps for Admins package from the AppExchange so you can review and modify the default security and access settings before rolling out the Salesforce1 Mobile App to your users.

When the Salesforce1 Connected Apps components are installed they're added to the Connected Apps section in Setup. Here, you can view and edit the settings for each of the apps, including user access with profiles, permissions, and IP range restrictions.

 

 

2. Enable Permissions

In Salesforce1, users can receive notifications in two ways: through notifications center in the app and via push notifications on their mobile device. These notifications occur when they are mentioned in Chatter posts or comments and when they receive approval requests.

To enable notifications for your org, navigate to Setup → Mobile Administration → Notifications → Settings. If they're not  already enabled, select "Enable in-app notifications" and "Enable push notifications" and save those settings.

One thing to keep in mind is that once you enable notifications for your org, your users can choose to disable push notifications specifically in their phone settings. Note that push notifications are not available in the Salesforce1 mobile browser experience.

Two types of notifications can appear to Salesforce1 users:

  • In-app notifications keep users aware of relevant activity while they're using Salesforce1. By tapping bell icon , a user can view the 20 most recent notifications received within the last 90 days.
  • If Salesforce Communities is enabled for your organisation, users see notifications from all communities they're members of. To help users easily identify which community a notification came from, the community name is listed after the time stamp.
  • Push notifications are alerts that appear on a mobile device when a user has installed the Salesforce1 downloadable app but isn't using it. These alerts can consist of text, icons, and sounds, depending on the device type. If an administrator enables push notifications for your organisation, users can choose individually whether to receive push notifications on their devices.

Note:  Some notifications include text that your users enter in Salesforce. To ensure that sensitive information isn't distributed through a third-party service without proper authorisation, push notifications include minimal content (such as a user's name) unless you enable full content in push notifications.

 

 

3. Enable Browser Permissions

The Salesforce1 Mobile App is available as a downloadable app on iOS and Android devices as well as a matching experience on mobile browsers. To enable the Salesforce1 experience on a mobile browser, navigate to Setup → Mobile Administration → Salesforce1 and select "Enable the Salesforce mobile browser app" so users are automatically redirected to the Salesforce mobile browser experience when they log in using a supported browser on an iOS or Android smartphone or tablet. To restrict this user experience, deselect this permission, and users will see the full Salesforce Mobile App as it appears on the desktop.

Customise for Your Company

You've made countless investments configuring Salesforce for your organisation.  Now, it's time to take some of those customisations and optimise them for mobile devices.  Here are a few things to think about as you determine what changes you'll need to make to your Salesforce implementation.

 

 

1. Get in the Mobile Mindset!

LESS IS MORE
Think about what the essential fields are when configuring object page layouts. Consider the mobile device screen real estate and move the most important information to the top and when possible only add the truly required fields.

THINK ABOUT "CLICKABILITY"
On a mobile device, consider how users will interact with the app when creating custom UIs. For example, buttons are easier to tap than links.

OPTIMISE FOR PAGE PERFORMANCE
When bringing custom pages and UIs to mobile, think about page performance. Are there images or processes that may cause slower page load times? Users are less patient with page performance on mobile devices, so streamline your content and keep your UI elements as lightweight as possible.

 

 

2. Revisit User Permissions

With App Cloud, all your customisations from the Web are brought to mobile, and therefore enforces the same CRUD (Create, Read, Update, Delete) permissions from your org for your users in the Salesforce1 App.

Once your users log into the Salesforce1 App, they'll have access to all the objects and apps they would normally have on the Web. They may be unfamiliar with some of the objects they see as they've been hidden for them on the Web using custom tab sets. A best practice to follow is to tweak CRUD permissions at the profile level to give users only what they need access to on the Web so they only see those objects on mobile.

 

 

3. Configure Your Layouts

Once you've done some basic configuration for the Salesforce1 mobile app, it's time to consider how to optimise layout in the full Salesforce desktop UI to give users the best possible mobile experience, like how fields are displayed on records.

PAGE LAYOUTS
When you view a record in Salesforce1, you see the fields, Visualforce pages, and related lists that are based on the record type and the user's profile in the full Salesforce desktop UI. Related lists show up as single-line cards containing the name of the page or related list.

Tapping the related list card displays its details. (Note that rich text area fields are not supported in the Salesforce1 Mobile App.)

You can also add expanded lookups and mobile-enabled Visualforce pages to the Mobile Cards section of your page layout to have them show up in the mobile card format in the Salesforce1 Mobile App. Note that these sections will only show up on the record's related information section in the Salesforce1 Mobile App and not in the full desktop UI.

COMPACT LAYOUTS
Compact layouts are a new way to display a record's key fields at a glance in the Salesforce1 Mobile App. Compact layouts determine which fields appear in Chatter feed item resulting from a record create action in the full desktop UI; and in the Salesforce1 Mobile App, compact layouts determine the fields shown in a record's highlights area, a record's preview card, and enhanced lookup cards on a record's related information page. You can customise an object's compact layout in the Customise section for an object in Setup.

For more information about how to customise page layouts and compact layouts, check out the Salesforce1 Admin Guide.

COMPACT LAYOUT TIPS
Compact layouts appear throughout various areas in the Salesforce1 Mobile App to help give more information about the records users are viewing, for example on the top header of a record or on an enhanced lookup card on the related information section of a record.

When configuring compact layouts, choose fields that are important and contain useful information to users. Real estate on a mobile device is small so make sure the fields in your compact layouts are small enough.

 

 

4. Customise Your Navigation Menu

Users access the Salesforce1 navigation menu by tapping nav icon. Depending on your organisation's settings, the menu can contain:

  • Canvas apps—Displays for organisations that have enabled a canvas app to appear in the Salesforce1 navigation menu.
  • Dashboards—Availability depends on edition and user permissions. If an administrator doesn't include it as a distinct node in the menu, it's automatically included in the set of Smart Search Items.
  • Events—Lists events that are owned by the user, that the user created for him- or herself, and that the user or a user's groups are invited to. With the exception of multiday events that haven't concluded, past events aren't available.
  • Feed—Displays for organisations that have Chatter enabled.
  • Flexible Pages—Custom Salesforce1 app home pages.
  • Groups—Displays for organisations that have Chatter enabled. If an administrator doesn't include it as a distinct node in the menu, then it's automatically included in the set of Smart Search Items.
  • People—Displays for organisations that have Chatter enabled. If an administrator doesn't include it as a distinct node in the menu, then it's automatically included in the set of Smart Search Items.
  • Smart Search Items—Represents a set of searchable objects the user has viewed or worked with recently in the full Salesforce site. These items display in the Recent section of the menu.

Note:  If your users don't yet have a history of recent objects, they initially see a set of default objects in the Recent section. It can take up to 15 days for objects users work with to appear in the Recent section. To make objects appear under Recent sooner, they can pin them from the search results screen in the full Salesforce site.

  • Tasks—Lists of a user's open and closed tasks, and tasks that have been delegated.
  • Today—An app that helps a user plan for and manage their day, by integrating their mobile calendar events with associated Salesforce tasks, accounts, and contacts, as well as allowing the user to instantly join conference calls, quickly log notes about events, and more. Available in the Salesforce1 downloadable apps only.
  • Visualforce page tabs

Note:  Only Visualforce pages with the Available for Salesforce mobile apps checkbox selected will display in Salesforce1.

Things to Keep in Mind

  • There isn't a way to set different menu configurations for different types of users.
  • Anything that is represented by a tab in Salesforce—such as standard and custom objects, Visualforce pages, the Feed, People, or Groups—is visible for a user in the Salesforce1 menu based on the user's profile settings. For example, if a user is assigned to a profile that has the Groups tab set to Tab Hidden, the user won't see the Groups menu item in Salesforce1, even though an administrator has included it in the menu.

Learn step by step how to customise your mobile navigation and configure Salesforce1 for your org with these simple product walk-throughs.

 

 

5. Setup Publisher Actions

The Publisher is the launchpad for your users to take valuable business actions in the context of what they're doing.  Actions are available in the standard browser UI as well as mobile-optimised for Salesforce1.

You can create standard actions that let users create or update records or log calls; and custom actions that integrate with a third-party application or include a custom Visualforce UI. When considering what actions you might want to create for Salesforce1, ask your users what they wish they could do in the mobile context. Publisher actions can be global or contextual.

In the Salesforce1 Mobile App, your users can access the publisher by tapping the 'plus' icon from their feed or any record page.

GLOBAL ACTIONS
Global actions - like creating a Chatter post, posting a file or photo, or creating a task - are configured in the Create → Global Actions area of Setup and are available wherever you access the publisher

OBJECT-SPECIFIC ACTIONS
Object-specific actions are configured in the Customise area of Setup under the object you want to initiate the action from. These actions are specific to the context of the record the user is on.

Once you create a publisher action, you can add it to the global publisher layout or object page layout in Setup. You can also configure different page layouts for different profiles.

Best Practices for Creating Publisher Actions
Ninety percent of your actions should be object-specific. Only use global actions if the action isn't tied to a specific object and users need to access it from anywhere in the app. When customising an action layout, add only the most essential fields. Minimalism is key when it comes to mobile layouts.  When adding labels to your publisher actions, use task-oriented names that tell your users what they do. Use action words like new, create, share, update, or import. Keep the labels short, but descriptive. There's no limit to the number of fields you can add to an action layout, but for an optimum user experience, add only the most important and required fields. An action's icon is tied to the icon for the object's tab in Salesforce. You can also upload your own custom icons.

Learn step by step how to setup publisher actions and customise your publisher layouts with these simple product walk-throughs.

*For more information about how to customise Publisher Actions, check out the Salesforce1 App Admin Guide.

 

 

Optimise Your Visualforce Pages

While Salesforce1 supports Visualforce pages, they are not all automatically mobile-friendly. The standard Salesforce header and sidebar are disabled in favor of the Salesforce1 UI, and JavaScript API is available to make it possible for Visualforce pages to connect with Salesforce1 navigation options. In other respects, the pages remain as they are, and although usable within Salesforce1, desktop-focused Visualforce pages will feel desktop-focused.

Fortunately, there are various tools and options to help optimise your Visualforce pages for mobile. You can either revise your code so that your pages work in both the full Salesforce site and the Salesforce1 app, or you can create mobile-specific pages.

Tips for Optimising Your Visualforce Pages:

  • Focus on optimising the Visualforce pages that users need the most when they're away from their desks. Not all your pages will need to be available on mobile devices.
  • Smaller pages work better on mobile devices. Optimise for fast load times and a smaller form factor.
  • Utilise a framework like JQuery Mobile to customise the look and feel of your pages for mobile
  • Think about responsive web design when it comes to styling your pages. Try not to use fixed widths so pages can adapt to the form factor they're accessed on.
  • Turn on Visualforce page caching for better page performance. To cache a page, set the cache attribute on the page to "true" and set a value (in seconds) in the expires attribute. For example <apex: page cache="true" expires="600">
  • To make a Visualforce page available in the Salesforce1 App, check the box for "Available for Salesforce mobile apps" in Setup for each page and don't forget to add it to the Navigation Menu in Setup.
  • Make sure your VF page has a tab and check the box for "Mobile Ready" on the tab settings

 

 

Install Mobile-Ready ISV Apps

Extend your Salesforce1 Mobile app with powerful mobile-ready partner apps! Check out the AppExchange to find, evaluate and install solutions for every department and industry.

 

 

Salesforce1 Mobile App Walkthroughs

Learn step by step how to set-up and configure Salesforce1 for your org with these simple product walk-throughs.

Salesforce1 Admin Rollout Guide › 1. Set-up the App for Your Users

Next  2. How to Use the App