Updated: September 20, 2018

Profile Header


The profile header helps the user recognize and learn more about a person. It may also allow the user to quickly contact that person without needing to drill down into his/her contact details.




Use the profile header within the object floorplan or on a user profile screen.


Do not include information in the header that is excessively long or overly detailed.



The profile header is comprised of several pieces of information about the person. The title is the only required piece in the profile header.

A. Image

Including an image is not required but is highly recommended, as this helps the user recognize the person in question.

B. Main Content

The main content section includes name and one additional piece of information about the person.

C. Additional Information

Additional information includes two short strings or a short paragraph of relevant text.

D. Action Icons

Action icons provides ways for the user to contact the person instantly.


In compact width, content in the profile header is always center-aligned. Given the limited space in compact width, when a description is present, action icons will not be displayed. As a designer, it is important that you decide whether the main purpose of this screen is to provide the user with a means to contact the person in question or rather to learn more about that person.



Action icons

When including action items, there can be minimum of 2 and a maximum of 5, though having this many is not recommended. Only present icons that are frequently-used in the current context. Apply a gray color to the action icon when it is disabled.


Tappable Name

The profile name will be in tint color if it is tappable. Use it as an entry point to drill in to more details about the person.


Action Button

As the name implies, an action button allows the user to perform an action on the current object. Common actions include adding an object to a list, starting an event with an object, or otherwise marking an object.

When an action button is tapped, it should adopt an active state; when it is tapped again, it should return to its inactive state. Button text should clearly communicate to the user what will happen when the button is tapped.

Please note that icons are also a recommended way to provide actions within the header.



The description section may include two short strings of text or a brief paragraph that displays two lines. If the paragraph is too long to be displayed on the header, consider moving it to the top of the content section.


In compact width, action buttons should be center-aligned with everything else in the header. Contact icons and the description section should not be included when an action button is present.