Your first App Key is created automatically when you install the PK4 TimeTracker application in your Salesforce org. That one App Key can be used for all the Time Tracker users in your org.
On the other hand, you can create multiple App Keys in your org to support different use-cases of PK4 TimeTracker. For example, if you have users tracking time for different objects in your org. Say, your field engineers want to track their time against service requests, while your Support team needs to track time against Cases. And your Sales team needs to track time against Opportunities. No problem - you can set up three separate App Keys and hand them over to each of those teams. Depending on which App Key a user uses to log in, the relevant configurations will kick in.
App Keys must typically be:
- Not long, but not too short. 8 to 10 characters work well.
- Unique. They need to be unique across the Salesforce system, so use a prefix that's unique to your org. maybe part of your domain name, followed by a sequence number.
- Not necessarily easy to remember. People won't need to remember the App Key they get - once they use it to log in, the browser or the mobile app they're using will automatically remember what they used last.
Setting up an App Key needs some thinking, since there are so many things you can configure. The screens have in-line help, so you can use that to make your selections.
Note:
- Share the App Key that you create with the users that need it, via email or another such mechanism.
- For users who work within Salesforce, set the App Key on the user's TT User record, so that App Key's configuration will kick in for that user when they log in.
Here's what the TT User screen looks like, for you to add an App Key.
