1 of 1 people found this helpful
User/client id- Every user who would access Remedyforce or Salesforce need to have login that is what the user is
Client is user. Just a verbiage in Remedyforce on calling requester as "Client Id"
They are same.
Account : Account comes from salesforce meaning "Business accounts are used to store information about companies or other entities" it could be used as location /department or for any logical grouping of customers.
Usex x may belong to BMC account or NY Account or IT Account.
When you pull the user on Remedyforce Incident form it auto populates account. Gives way of reporting or using SLA or showing company related issues.
Account is not Required. Its optional but useful.
Profile : When you create users, you assign a profile to each one. Profiles define how users access objects and data, and what they can do within the application. Basically it controls when user logs in what they will see like tabs, what type of access they will have. RF comes with profiles like ServiceDesk Staff , Service DeskClient
You will need profile for each user. Its like assigning set of permissions.
Role: This is optional. You can completely ignore this unless you are using some other Salesforce products or you have sharing needs. Salesforce offers a user role hierarchy that you can use together with sharing settings to determine the levels of access users have to your organization’s data. Roles within the hierarchy affect access on key components like records and reports
Queue: This is like groups to whom the Incident /Task CR or Problems woudl be assigned. So every saff will belong to a Queue say Help desk, NOC,Database,HR . Queue will take ownership of issue and then it would be assigned to agent from that queue
View: (if you are referring to Remedyforce views) View is nothing but a way of filtering data on Console. For example I may like to see only open Incidents so I may need view for that with condition which says showw me only open issues. Views are snap shot o data based on requirements.
There is content on this topic however you may like put these together
User is client id , client/user may belong to an account. To create user you need a profile which decides what type of access they have. Roles are optional for record sharing etc. Queue are needed by agents to group them in service verticals. Views are just way of looking at data.
Hope this gives you some more clarity.
This is perfect! Thank you.
I wish it was spelled out this simply in the documentation.