Wiki 1stAnswer Help

User Tools

Site Tools

Trace:
en:admin:rights

Warning: Trying to access array offset on value of type bool in /is/htdocs/wp13465426_9ILOTLR0N8/www/help1stanswernew/inc/html.php on line 1164

Warning: Trying to access array offset on value of type bool in /is/htdocs/wp13465426_9ILOTLR0N8/www/help1stanswernew/inc/html.php on line 1168

Warning: Trying to access array offset on value of type bool in /is/htdocs/wp13465426_9ILOTLR0N8/www/help1stanswernew/inc/html.php on line 1171

Warning: Trying to access array offset on value of type bool in /is/htdocs/wp13465426_9ILOTLR0N8/www/help1stanswernew/inc/html.php on line 1172

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
en:admin:rights [2015/08/19 11:54]
wbuchner [E-Mail Quality Assurance] 		en:admin:rights [2017/12/27 15:17] (current)
Line 16: Line 16:
 |Analysis.Display.MalfunctionReport|Allows the user to access the "Malfunction" report.  |  4.1.1  | |Analysis.Display.MalfunctionReport|Allows the user to access the "Malfunction" report.  |  4.1.1  |
 |Analysis.Display.ProblemExport|Allows the user to access Problem  Export.  |  4.1.1  | |Analysis.Display.ProblemExport|Allows the user to access Problem  Export.  |  4.1.1  |
-|Analysis.Display.ProblemRealTimeMonitor|Allows the user to access the "Problem Realtime Monitor" report= Number of problems in the selected category and status.  |  4.1.1  |+|Analysis.Display.ProblemRealTimeMonitor|Allows the user to access the "Problem Realtime Monitor" report= Number of problems in the selected category and status.  |  4.1.1 - 6.0  |
 |Analysis.Display.RawDataExport|In principle, the user can export data to Excel. Additional rights are necessary to release each raw data export to the user.  |  4.1.1  | |Analysis.Display.RawDataExport|In principle, the user can export data to Excel. Additional rights are necessary to release each raw data export to the user.  |  4.1.1  |
 |Analysis.Display.RawDataExport.Case|The user can export all Incident data to Excel. Prerequisite: He has the right "Analysis.Display.­RawDataExport". Right also applies for incident pools.  |  5.2.1  | |Analysis.Display.RawDataExport.Case|The user can export all Incident data to Excel. Prerequisite: He has the right "Analysis.Display.­RawDataExport". Right also applies for incident pools.  |  5.2.1  |
Line 35: Line 35:
 |Analysis.Display.RawDataExport.TimeTracking|The user can export activity recordings to Excel. Prerequisite: He has the right "Analysis.Display.RawDataExport".  |  4.3.1  | |Analysis.Display.RawDataExport.TimeTracking|The user can export activity recordings to Excel. Prerequisite: He has the right "Analysis.Display.RawDataExport".  |  4.3.1  |
 |Analysis.Display.ReactionTime|Allows the user to access the Reaction Time report. Prerequisite: He has the right Analysis.Display.SolutionTime.|  4.1.1  | |Analysis.Display.ReactionTime|Allows the user to access the Reaction Time report. Prerequisite: He has the right Analysis.Display.SolutionTime.|  4.1.1  |
-|Analysis.Display.RealTimeMonitor|Allows the user to access Realtime-Monitor.  |  4.1.1  |+|Analysis.Display.RealTimeMonitor|Allows the user to access Realtime-Monitor.  |  4.1.1 - 6.0  |
 |Analysis.Display.RequestForChangesReport|Allows the user to access the "Request For Change" report.  |  4.1.1  | |Analysis.Display.RequestForChangesReport|Allows the user to access the "Request For Change" report.  |  4.1.1  |
 |Analysis.Display.ServiceTaskReport|Allows the user to access the "Service Task" report.  |  4.1.1  | |Analysis.Display.ServiceTaskReport|Allows the user to access the "Service Task" report.  |  4.1.1  |
Line 46: Line 46:
 ^Right^Description^Version^ ^Right^Description^Version^
 |Case.AdminMode|The user has no limitations for support level and support categories. In addition to that, he can open all Incidents, even if the Incident is private or does not belong to his assigned support category.  |  4.1.1  | |Case.AdminMode|The user has no limitations for support level and support categories. In addition to that, he can open all Incidents, even if the Incident is private or does not belong to his assigned support category.  |  4.1.1  |
 +|Case.AiRecommendation.Category|The user gets recommendations for categories from AI (AI must be configured) | 6.0.15.0 |
 +|Case.AiRecommendation.Relation|The user gets recommendations for similar incidents in the "relations" tab (AI must be configured) | 6.0.15.0 |
 +|Case.AiRecommendation.Solution|The user gets recommendations for solutions from similar tickets (AI must be configured) | 6.0.15.0 |
 |<del>Case.Assign</del>|Is no longer used  | <del> 4.0.14 </del> | |<del>Case.Assign</del>|Is no longer used  | <del> 4.0.14 </del> |
 |Case.Assign.Takeover|The user can assign himself an Incident, which has already been assigned to someone else.  |  4.1.1  | |Case.Assign.Takeover|The user can assign himself an Incident, which has already been assigned to someone else.  |  4.1.1  |
Line 101: Line 104:
 |<del>Case.MarkAsDuplicate</del>|Is not longer used  | | |<del>Case.MarkAsDuplicate</del>|Is not longer used  | |
 |Case.Message.Display.Private|Allows to display private emails in course of solution and [from 5.4] in the E-Mail-Pool. Private emails are either emails which are generated by the system (which are only send to users) or all emails, which have been selected as "private".  |  4.1.1  | |Case.Message.Display.Private|Allows to display private emails in course of solution and [from 5.4] in the E-Mail-Pool. Private emails are either emails which are generated by the system (which are only send to users) or all emails, which have been selected as "private".  |  4.1.1  |
-|Case.Message.Create.Private|The user can change the a email message from private to public in CourseOfSolution.  |  4.1.1  |+|Case.Message.Create.Private|1. The user can change the a email message from private to public in CourseOfSolution. \\ 2. The user is allowed to mark mails and sms as internal when sending them (since 5.9.4.0)  |  4.1.1  |
 |Case.Open.AllInMyCategories|The user can open all Incidents of a category which are assigned to him. Without this right a user can only open the Incidents whose customer he is.  |  4.1.1  | |Case.Open.AllInMyCategories|The user can open all Incidents of a category which are assigned to him. Without this right a user can only open the Incidents whose customer he is.  |  4.1.1  |
 |Case.Open.ReadOnly|The user can open an Incident in read-only mode (which he has access to via his support team and his support level) also when this Incident is  assigned to a different user.  |  4.1.1  | |Case.Open.ReadOnly|The user can open an Incident in read-only mode (which he has access to via his support team and his support level) also when this Incident is  assigned to a different user.  |  4.1.1  |
-|Case.Owner|The user can be the executive person of a incident.  |  5.3.8  |+|Case.Owner|The user can be the executive person of a incident. Users are only displayed as responsible if they are a supportteam member of a supportteam of the category. This right could be restricted by the setting supportTeamDependantCaseOwner and supportLevelDependantCaseOwner. ([[http://help.1stanswer.de/doku.php?id=admin:start:v5-7:einstellungen-beschreibung|Settings]])  |  5.3.8  |
 |Case.Owner.Display|The user can view the executive persons of a incident and search after it. Adding a executive is only in combination with the right **Case.Edit** possible  |  5.3.8  | |Case.Owner.Display|The user can view the executive persons of a incident and search after it. Adding a executive is only in combination with the right **Case.Edit** possible  |  5.3.8  |
 |Case.Poll.Display|The user can see the tab 'Feedback' at the Incident.  |  4.1.1  | |Case.Poll.Display|The user can see the tab 'Feedback' at the Incident.  |  4.1.1  |
Line 114: Line 117:
 |Case.ProblemAndKBAList.Display|The user can see the "Problems and KBAs" Panel in the Incident and can build relations to existing Problems.  |  4.1.1  | |Case.ProblemAndKBAList.Display|The user can see the "Problems and KBAs" Panel in the Incident and can build relations to existing Problems.  |  4.1.1  |
 |Case.PSC.Display|Displays the panel for the creation and the verification of the PIN of a Premium Service Card in an Incident.  |  4.1.1  | |Case.PSC.Display|Displays the panel for the creation and the verification of the PIN of a Premium Service Card in an Incident.  |  4.1.1  |
-|Case.QuickSearch|Displays the quick search of an Incident via the ID number in the Incident pool.  |  4.1.1  |+|Case.QuickSearch|Allows searching for Incidents with the Quicksearch in the menu. |  4.1.1 / 6.0.31  |
 |<del>Case.Quote.Create</del>|Is no longer used  |  <del>4.1.22</del>  | |<del>Case.Quote.Create</del>|Is no longer used  |  <del>4.1.22</del>  |
 |Case.ReactionTime|The user can protocol a feedback to a customer as a time stamp in the History.  |  4.1.1  | |Case.ReactionTime|The user can protocol a feedback to a customer as a time stamp in the History.  |  4.1.1  |
Line 158: Line 161:
 |Case.SapServiceNotification.Create | The user can create a SAP service notification from an incident.|  5.1.16  | |Case.SapServiceNotification.Create | The user can create a SAP service notification from an incident.|  5.1.16  |
 |Case.SapServiceNotification.Display | The user can see relations between incidents and SAP service notifications|  5.1.16  | |Case.SapServiceNotification.Display | The user can see relations between incidents and SAP service notifications|  5.1.16  |
-|Case.SupportTeam.Display |The user can see the assigned SupportTeam. | 5.4 |+|Case.SupportTeam.Display |The user can see the assigned SupportTeam. |  5.4  |
 |Case.SendToSpecifiedLevel |Allows the user to push incidents into an level. |  5.6  | |Case.SendToSpecifiedLevel |Allows the user to push incidents into an level. |  5.6  |
 +|Case.ConfigurationItemPanel.Configure|Allows the user to configure the ci panel in incident detail|  5.3  |
 +|Case.Email.MarkAsSolution| An E-Mail can be marked as solution |  ?  |
 +|Case.Comment.MarkAsSolution| A Comment/SAP-Notification/Reject reason can be marked as solution |  ?  |
 +|Case.Solution.MarkAsSolution| A solution can be marked as solution |  ?  |
 +|Case.Email.MarkAsProblemDescription| An E-Mail can be marked as problem description |  ?  |
 +|Case.Comment.MarkAsProblemDescription| A Comment/SAP-Notification/Reject reason can be marked as problem description |  ?  |
 +|Case.Solution.MarkAsProblemDescription| A solution can be marked as problem description |  ?  |
 ===== Change Management ===== ===== Change Management =====
  
Line 207: Line 217:
 |CI.Display.MyCompanyHierarchy|The user can see the CI master data of the customers of his company, the one of the menial companies and his own ones.  |  5.1.8  | |CI.Display.MyCompanyHierarchy|The user can see the CI master data of the customers of his company, the one of the menial companies and his own ones.  |  5.1.8  |
 |CI.Display.All|The user can see all CI master data.  |  5.1.8  | |CI.Display.All|The user can see all CI master data.  |  5.1.8  |
 +|CI.QuickSearch|Allows searching for CIs with the Quicksearch in the menu. | 6.0.31  |
 |CI.Display.Tasks|The user can see the 'Task'-tab at the CI detailview.  |  4.1.1  | |CI.Display.Tasks|The user can see the 'Task'-tab at the CI detailview.  |  4.1.1  |
 |CI.Display.Problems|The user can see the 'Problems'-tab at the CI detailview.  |  4.1.1  | |CI.Display.Problems|The user can see the 'Problems'-tab at the CI detailview.  |  4.1.1  |
Line 223: Line 234:
 |Company.Edit| The user can change company informations and company relations.  |  5.1.10  | |Company.Edit| The user can change company informations and company relations.  |  5.1.10  |
 |Company.SavedSearches|Allows the user to publish saves searches. |  5.4  | |Company.SavedSearches|Allows the user to publish saves searches. |  5.4  |
 +|Company.QuickSearch|Allows searching for companies with the Quicksearch in the menu. | 6.0.31  |
  
 ===== Master data ===== ===== Master data =====
Line 237: Line 249:
 |Customer.Display.MyCompanyHierarchy|The user can see the master data of the customers of his company, the one of the menial companies and only the master data of his company and the menial companies.  |  5.1.8  | |Customer.Display.MyCompanyHierarchy|The user can see the master data of the customers of his company, the one of the menial companies and only the master data of his company and the menial companies.  |  5.1.8  |
 |Customer.Display.All|The user can see the master data of all customers and sompanies.  |  5.1.8  | |Customer.Display.All|The user can see the master data of all customers and sompanies.  |  5.1.8  |
 +|Customer.QuickSearch|Allows searching for customers with the Quicksearch in the menu. | 6.0.31  |
 |<del>Customer.Display.ContactCaseHistory </del> renamed| |  4.1.1  | |<del>Customer.Display.ContactCaseHistory </del> renamed| |  4.1.1  |
 |<del>Customer.Display.CompanyCaseHistory</del>|Furthermore, a customer with a Login for 1stAnswer can view and open the Incidents for his company (via the external company number) in the My Incident List.  |  4.0.13; since 5.1.8  matched with company concept  | |<del>Customer.Display.CompanyCaseHistory</del>|Furthermore, a customer with a Login for 1stAnswer can view and open the Incidents for his company (via the external company number) in the My Incident List.  |  4.0.13; since 5.1.8  matched with company concept  |
Line 245: Line 258:
 |<del>Customer.Search</del>|Is not longer used. Replaced with the "Customer.Display.*" rights.  |  4.1.1  | |<del>Customer.Search</del>|Is not longer used. Replaced with the "Customer.Display.*" rights.  |  4.1.1  |
 |Customer.Search.Deleted|The user can search for deleted customers in the master data.  |  4.1.1  | |Customer.Search.Deleted|The user can search for deleted customers in the master data.  |  4.1.1  |
-|Customer.Tasks.Display| |  4.1.1  |+|Customer.Tasks.Display| Visibility of task panel in customer cockpit. (deprecated) |  4.1.1  |
 |Customer.Cockpit.Add| Allows the User to add new cockpits in CustomerCockpit.  |  4.1.1  | |Customer.Cockpit.Add| Allows the User to add new cockpits in CustomerCockpit.  |  4.1.1  |
 |Customer.Cockpit.Delete| Allows the User delete existing Customer Cockpits.  |  4.1.1  | |Customer.Cockpit.Delete| Allows the User delete existing Customer Cockpits.  |  4.1.1  |
Line 259: Line 272:
 |Contract.Edit|Allows the User to edit contracts.  |  5.2.1  | |Contract.Edit|Allows the User to edit contracts.  |  5.2.1  |
 |Contract.SavedSearches|Allows the User to saving contract searches.  |  5.2.1  | |Contract.SavedSearches|Allows the User to saving contract searches.  |  5.2.1  |
 +|Contract.QuickSearch|Allows searching for contracts with the Quicksearch in the menu. | 6.0.31  |
  
 ===== Administration ===== ===== Administration =====
Line 284: Line 298:
 |InterfaceConfiguration.ShowAllMandators|The user can manage existing configuration files for all mandators  |  5.1.18  | |InterfaceConfiguration.ShowAllMandators|The user can manage existing configuration files for all mandators  |  5.1.18  |
 |LogFiles.Display|The user can look at and download Log-files at the administration.  |  5.3.1  | |LogFiles.Display|The user can look at and download Log-files at the administration.  |  5.3.1  |
 +|LogSettings.Display|The user can look at and change Log-Settings at the administration.  |  7.0.13.0  |
 |Poll.Display|Allows to display customer surveys.  |  4.1.1  | |Poll.Display|Allows to display customer surveys.  |  4.1.1  |
 |Poll.Manage|Allows to administrate customer surveys (Add, change, delete, set active).  |  4.1.1  | |Poll.Manage|Allows to administrate customer surveys (Add, change, delete, set active).  |  4.1.1  |
Line 295: Line 310:
 |Role.Edit|The user can edit and save an existing role.  |  4.1.1  | |Role.Edit|The user can edit and save an existing role.  |  4.1.1  |
 |Role.Search|The user can search for roles in the system.  |  4.1.1  | |Role.Search|The user can search for roles in the system.  |  4.1.1  |
-|Settings.Display|The user can look at global settings, mandators and webconfig at the administration.  |  5.3.1  | +|Settings.Display|The user can look at global settings, mandators and webconfig at the administration.  |  5.3.1 - 5.6 | 
-|Settings.GlobalSettings.Display|The user can look at global settings at the administration.  |  5.3.1  | +|Settings.GlobalSettings.Display|The user can look at global settings at the administration.  |  5.3.1 - 5.6  | 
-|Settings.GlobalSettings.Edit|The user can look at and edit global settings at the administration.  |  5.3.1  | +|Settings.GlobalSettings.Edit|The user can look at and edit global settings at the administration.  |  5.3.1 - 5.6  | 
-|Settings.Mandator.Display|The user can look at mandators at the administration.  |  5.3.1  | +|Settings.Mandator.Display|The user can look at mandators at the administration.  |  5.3.1 - 5.6  | 
-|Settings.Mandator.Edit|The user can look at and edit mandators at the administration.  |  5.3.1  | +|Settings.Mandator.Edit|The user can look at and edit mandators at the administration.  |  5.3.1 - 5.6  | 
-|Settings.Mandator.Add|The user can look at, edit and add new mandators at the administration.  |  5.3.1  | +|Settings.Mandator.Add|The user can look at, edit and add new mandators at the administration.  |  5.3.1 - 5.6  | 
-|Settings.WebConfig.Display|The user can look at webconfig at the administration.  |  5.3.1  | +|Settings.WebConfig.Display|The user can look at webconfig at the administration.  |  5.3.1 - 5.6  | 
-|Settings.WebConfig.Edit|The user can look at and edit webconfig at the administration.  |  5.3.1  |+|Settings.WebConfig.Edit|The user can look at and edit webconfig at the administration.  |  5.3.1 - 5.6  | 
 +| Settings.AddNode | It is possible to add further nodes in settings (z.B. incoming Nodes - IntelligentEmail) | > 5.7 | 
 +| Settings.Edit | Settings can be edited. | > 5.7 | 
 +| Settings.MandatorIndependent.Display | Mandator independent settings are visible. | > 5.7 | 
 +| Settings.MandatorIndependent.Edit | Mandator independent settings can be edited. | > 5.7 | 
 +| Settings.RemoveNode | It is possible to remove nodes in settings (z.B. incoming Nodes - IntelligentEmail)  | > 5.7 |
 |<del>SolutionClassification.Display</del>|This right has been renamed. New name Classification.Display.  |  4.1.1  | |<del>SolutionClassification.Display</del>|This right has been renamed. New name Classification.Display.  |  4.1.1  |
 |<del>SolutionClassification.Edit</del>|This right has been renamed. New name Classification.Edit.  |  4.1.1  | |<del>SolutionClassification.Edit</del>|This right has been renamed. New name Classification.Edit.  |  4.1.1  |
Line 390: Line 410:
 |Problem.Private.Change|The user can change the label "Private" of a Problem later on.  |  4.1.1  | |Problem.Private.Change|The user can change the label "Private" of a Problem later on.  |  4.1.1  |
 |Problem.Problem.Change|The user can change the Problem description later on.  |  4.1.1  | |Problem.Problem.Change|The user can change the Problem description later on.  |  4.1.1  |
-|Problem.QuickSearch|Displays the quick search of a problem via the Problem number in the Problem Pool.  |  4.1.1  |+|Problem.QuickSearch|Allows searching for problems with the Quicksearch in the menu. | 4.1.1 / 6.0.31  |
 |Problem.Reject|The user can reject a problem.  |  4.1.1  | |Problem.Reject|The user can reject a problem.  |  4.1.1  |
 |Problem.Reopen|The user can reopen a problem.  |  4.1.1  | |Problem.Reopen|The user can reopen a problem.  |  4.1.1  |
Line 429: Line 449:
 |ServiceCall.Complete | The user can set the servicecall to status "complete".  |  4.1.1  | |ServiceCall.Complete | The user can set the servicecall to status "complete".  |  4.1.1  |
 |ServiceCall.Display | The user can open a service call.  |  4.1.1  | |ServiceCall.Display | The user can open a service call.  |  4.1.1  |
 +|ServiceCall.QuickSearch|Allows searching for service calls with the Quicksearch in the menu. | 6.0.31  |
 |ServiceCall.Edit | The user can edit the service call as far as the status of the service call allow this.  |  4.1.1  | |ServiceCall.Edit | The user can edit the service call as far as the status of the service call allow this.  |  4.1.1  |
 |ServiceCall.History.Display | The user can see the service call history.  |  4.1.1  | |ServiceCall.History.Display | The user can see the service call history.  |  4.1.1  |
Line 510: Line 531:
 |MailConfiguration.Advanced|Allows the user to edit the advanced settings (for example category specific settings) of all business objects.| 5.4 | |MailConfiguration.Advanced|Allows the user to edit the advanced settings (for example category specific settings) of all business objects.| 5.4 |
 |MailConfiguration.Mandator|Allows the user to change the mandator specific mail settings.| 5.4 | |MailConfiguration.Mandator|Allows the user to change the mandator specific mail settings.| 5.4 |
 +|MailConfiguration.General|Allows the users to change their general mail settings.| 5.4 |
 ===== E-Mail Quality Assurance ===== ===== E-Mail Quality Assurance =====
  
Line 523: Line 544:
  
 ^Right^Description^Version^ ^Right^Description^Version^
-|Chat.Display|Allows the user to use the service chat. |  5.5  | +|<del>Chat.Display</del>|Allows the user to use the service chat. |  5.5 [Removed in 5.9]  | 
-|Chat.Disable|Allows the user to disable the service chat manually. |  5.5  | +|<del>Chat.Disable</del>|Allows the user to disable the service chat manually. |  5.5 [Removed in 5.9]  |
 ===== Configuration-Item Service-Tasks===== ===== Configuration-Item Service-Tasks=====
 ^Right^Description^Version^ ^Right^Description^Version^
en/admin/rights.1439978055.txt.gz · Last modified: 2015/08/19 11:54 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki