PATH:
home
/
centosnipponia
/
public_html
/
ticketing.nipponia.com
/
include
/
i18n
/
fa
/
help
/
tips
#This is popup help messages for the Admin Panel -> Settings -> Users #Fields: #title - Shown in bold at the top of the popover window #content - The body of the help popover #links - List of links shows below the content #title - Link title #href - href of link (links starting with / are translated to the #helpdesk installation path) #The key names such as 'helpdesk_name' should not be translated as they #must match the HTML #ids put into the page template. #General Settings --- client_name_format: title: قالب پیش فرض نمایش نام کارشناسان content: > قالب نمایش نام کارشناسان را در کل سیستم مشخص کنید. نمونه های ایمیل هم از همین قالب استفاده می کنند اگر قالب دیگری برایشان تنظیم نشده باشد. #Authentication settings client_password_policy: title: قوانین مدیریت رمز عبور content: > یک <span class="doc-desc-title">قانون رمز عبور</span> برای <span class="doc-desc-title">کاربرها</span> انتخاب کنید. با نصب افزونه های <span class="doc-desc-title">قانون رمز عبور </span>، می توان قوانین بیشتر را اضافه کرد. client_session_timeout: title: مهلت جلسه کاربر content: > حداکثر زمان بیکار(به دقیقه) برای نیاز به ورود دوباره را انتخاب کنبد.<br><br> اگر می خواهید <span class="doc-desc-title">وقفه ی نشست کارکنان</span> راذ غیر فعال کنید ، 0 وارد کنید. registration_method: title: گزینه های ثبت نام content: > <span class="doc-desc-title">Registration Method</span> and <span class="doc-desc-title">Registration Required</span> are used together to configure how users register and access the web portal of your help desk. The table below summarizes how the two settings are interpreted by the system. <table border="1" cellpadding="2px" cellspacing="0" style="margin-top:7px" ><tbody style="vertical-align:top;"> <tr><th>Registration Required</th> <th>Registration Method</th> <th>Result</th></tr> <tr><td>No</td><td>Public</td> <td>Registration encouraged but not required for new tickets.</td></tr> <tr><td>Yes</td><td>Public</td> <td>Registration and login are required for new tickets</td></tr> <tr><td>No</td><td>Private</td> <td>Anyone can create a ticket, but only agents can register accounts</td></tr> <tr><td>Yes</td><td>Private</td> <td>User access is by invitation only</td></tr> <tr><td>No</td><td>Disabled</td> <td>No one can register for an account, but anyone can create a ticket. <em>This was how osTicket functioned prior to 1.9</em></td></tr> <tr><td>Yes</td><td>Disabled</td> <td>Disable new tickets via web portal</td></tr> </tbody></table> client_verify_email: title: نیاز به تایید ایمیل content: > Disable this option to give your users immediate access to tickets via the "Check Ticket Status" login page in the client portal. If enabled, (which is the default), users will be required to receive an email and follow a link in the email to view the ticket. <br><br> Disabling email verification might allow third-parties (e.g. ticket collaborators) to impersonate the ticket owner. allow_auth_tokens: title: فعال کردن تایید نشانه (توکن) content: > فعال کردن این گزینه اجازه استفاده از کدهای تأیید اعتبار به کاربران برای ورود خودکار بر روی لینک تیکت کلیک کنید.
[+]
..
[-] manage.helptopic.yaml
[edit]
[-] install.yaml
[edit]
[-] tickets.queue.yaml
[edit]
[-] emails.banlist.yaml
[edit]
[-] settings.tasks.yaml
[edit]
[-] settings.users.yaml
[edit]
[-] dashboard.my_profile.yaml
[edit]
[-] staff.departments.yaml
[edit]
[-] emails.diagnostic.yaml
[edit]
[-] org.yaml
[edit]
[-] forms.yaml
[edit]
[-] staff.yaml
[edit]
[-] settings.kb.yaml
[edit]
[-] staff.agents.yaml
[edit]
[-] staff.team.yaml
[edit]
[-] staff.agent.yaml
[edit]
[-] settings.autoresponder.yaml
[edit]
[-] staff.staff_members.yaml
[edit]
[-] knowledgebase.category.yaml
[edit]
[-] settings.agents.yaml
[edit]
[-] settings.alerts.yaml
[edit]
[-] manage.custom_list.yaml
[edit]
[-] emails.email.yaml
[edit]
[-] dashboard.audit_logs.yaml
[edit]
[-] staff.department.yaml
[edit]
[-] manage.api_keys.yaml
[edit]
[-] manage.pages.yaml
[edit]
[-] dashboard.dashboard.yaml
[edit]
[-] dashboard.system_logs.yaml
[edit]
[-] tasks.queue.yaml
[edit]
[-] settings.ticket.yaml
[edit]
[-] knowledgebase.canned_response.yaml
[edit]
[-] manage.sla.yaml
[edit]
[-] settings.pages.yaml
[edit]
[-] emails.template.yaml
[edit]
[-] settings.email.yaml
[edit]
[-] staff.groups.yaml
[edit]
[-] knowledgebase.faq.yaml
[edit]
[-] dashboard.staff_directory.yaml
[edit]
[-] manage.schedule.yaml
[edit]
[-] settings.system.yaml
[edit]
[-] manage.filter.yaml
[edit]