Unified settings for multiple account types

Abstract

Account types that support one or more data classes (e.g., email, contacts, calendar, instant messaging) can be added and configured on a mobile device using a unified settings user interface. The user interface allows the user to easily activate and deactivate one or more data classes for an account type. The user interface can support one or more predefined account types and can allow the user to add and configure new account types. Visual indicators are provided in the user interface to remind the user of the data classes that are active on the mobile device for a particular account. Users can configure settings that effect a particular data class in all accounts on the mobile device. Users can also configure settings that are specific to a particular account.

1 . (canceled) 
     
     
         2 . A method comprising:
 adding a first account of a first account type on a mobile device, wherein the first account type supports a first plurality of data classes;   adding a second account of a second account type on the mobile device, wherein the second account type supports a second plurality of data classes, and wherein the second plurality of data classes and the first plurality of data classes include a same data class;   activating or deactivating the same data class for the first account, in response to receiving a first input through a user interface of the mobile device; and   activating or deactivating the same data class for the second account, in response to receiving a second input through the user interface, regardless of whether the same data class is activated or deactivated for the first account.   
     
     
         3 . The method of  claim 2 , wherein the first account and the second account are different accounts of a same account type. 
     
     
         4 . The method of  claim 2 , wherein the first account and the second account are different accounts of different account types. 
     
     
         5 . The method of  claim 2 , wherein the first account is preconfigured on the mobile device to be associated with the same data class, and wherein the second account is not preconfigured on the mobile device to be associated with the same data class. 
     
     
         6 . The method of  claim 5 , wherein adding the second account includes receiving an input to associate the second account with the same data class. 
     
     
         7 . The method of  claim 2  further comprising:
 configuring a data class setting of the same data class; and 
 applying, in response to configuring the data class setting, the data class setting to the same data class for the first account and the second account. 
 
     
     
         8 . The method of  claim 7 , wherein the data class setting is a sync setting and the same data class is a calendar data class to cause the calendar data class for the first account and the second account to synchronize. 
     
     
         9 . A non-transitory machine readable medium storing instructions, which when executed by one or more processors of a mobile device, cause the mobile device to perform a method comprising:
 adding a first account of a first account type on a mobile device, wherein the first account type supports a first plurality of data classes;   adding a second account of a second account type on the mobile device, wherein the second account type supports a second plurality of data classes, and wherein the second plurality of data classes and the first plurality of data classes include a same data class;   activating or deactivating the same data class for the first account, in response to receiving a first input through a user interface of the mobile device; and   activating or deactivating the same data class for the second account, in response to receiving a second input through the user interface, regardless of whether the same data class is activated or deactivated for the first account.   
     
     
         10 . The non-transitory machine readable medium of  claim 9 , wherein the first account and the second account are different accounts of a same account type. 
     
     
         11 . The non-transitory machine readable medium of  claim 9 , wherein the first account and the second account are different accounts of different account types. 
     
     
         12 . The non-transitory machine readable medium of  claim 9 , wherein the first account is preconfigured on the mobile device to be associated with the same data class, and wherein the second account is not preconfigured on the mobile device to be associated with the same data class. 
     
     
         13 . The non-transitory machine readable medium of  claim 12 , wherein adding the second account includes receiving an input to associate the second account with the same data class. 
     
     
         14 . The non-transitory machine readable medium of  claim 9  further comprising:
 configuring a data class setting of the same data class; and 
 applying, in response to configuring the data class setting, the data class setting to the same data class for the first account and the second account. 
 
     
     
         15 . A mobile device, comprising:
 a display to present a user interface to a user;   a memory storing executable instructions; and   one or more processors coupled to the memory and configured to execute the executable instructions to cause the mobile device to:
 add a first account of a first account type on the mobile device, wherein the first account type supports a first plurality of data classes, 
 add a second account of a second account type on the mobile device, wherein the second account type supports a second plurality of data classes, and wherein the second plurality of data classes and the first plurality of data classes include a same data class, 
 activate or deactivate the same data class for the first account, in response to receiving a first input through the user interface of the mobile device, and 
 activate or deactivate the same data class for the second account, in response to receiving a second input through the user interface, regardless of whether the same data class is activated or deactivated for the first account. 
   
     
     
         16 . The mobile device of  claim 15 , wherein the first account and the second account are different accounts of a same account type. 
     
     
         17 . The mobile device of  claim 15 , wherein the first account and the second account are different accounts of different account types. 
     
     
         18 . The mobile device of  claim 15 , wherein the first account is preconfigured on the mobile device to be associated with the same data class, and wherein the second account is not preconfigured on the mobile device to be associated with the same data class. 
     
     
         19 . The mobile device of  claim 15 , wherein the one or more processors are further configured to execute the executable instructions to cause the mobile device to:
 configure a data class setting of the same data class, and   apply, in response to configuring the data class setting, the data class setting to the same data class for the first account and the second account.   
     
     
         20 . The mobile device of  claim 19 , wherein the data class setting is a sync setting and the same data class is a calendar data class to cause the calendar data class for the first account and the second account to synchronize.