janishutz/libreevent
1
0
Fork 0
mirror of https://github.com/janishutz/libreevent.git synced 2025-11-25 13:24:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

add some compiled html files

Browse Source
This commit is contained in:
Janis Hutz
2023-06-17 14:12:31 +02:00
parent 00a7aaa08f
commit 1b794e0742
27 changed files with 691 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
website/dist/docs/admin-panel/settings/index.html vendored Normal file
View File

@@ -0,0 +1,42 @@
<!DOCTYPE html>
<html>
<head>
<title>Settings :: docs - libreevent</title>
<link rel="stylesheet" href="/css/style.css">
<link rel="stylesheet" href="/css/home.css">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta charset="utf-8">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.6.1/jquery.min.js"></script>
<script src="/docs/js/index.js"></script>
<link rel="stylesheet" href="/docs/css/style.css">
</head>
<body>
<div id="side-bar"></div>
<div id="nav"></div>
<div id="docPage">
<div id="doc-container">
<h1>Settings</h1>
<h2>2FA</h2>
<p>libreevent offers two different 2fa modes:</p>
<ul>
<li>Standard mode: The user has to click on a link that was sent to him via email. He'll automatically be logged in as soon as the page loads.</li>
<li>Enhanced mode: The user has to click on a link that was sent to him via email and then has to confirm it by entering the code that is shown to him on the 2FA page. After that he'll automatically be logged in.</li>
</ul>
<p>In both modes, the system informs the user about the IP address that tried to log into the account.</p>
<p>This setting can be changed individually for admin and user accounts and 2FA can be disabled entirely. It is highly encouraged to enable this at least for the admin accounts and for user accounts set the requirement to 'User-defined' or 'Always required' instead of 'Disabled'.</p>
<h2>User account passwords</h2>
<p>Here you may set password requirements for the user accounts. The system will always be offering the users to generate a password that is strong for them to facilitate the process of setting a password.</p>
<h2>Guest purchase</h2>
<p>Choose if a user may purchase a ticket without creating an account. An email address is always required as the system sends the tickets via email to the customers for easier access.</p>
<h2>Allow overbooking</h2>
<p>Activate this and set a percentage of overbooking, if you want to enable overbooking of the event to ensure that every single spot is occupied even if somebody does not show up. Use is strongly discouraged and currently only works with events that have no seating plan.</p>
<h2>Special requirements</h2>
<p>Here you may set a special requirement that a person booking a ticket has to fulfill, like the email address has to be ending in @yourdomain.com or they need to live in a certain street / town / city / country in order for them to be allowed to buy a ticket. You may also require that they provide a certain number, code or similar. Finally, you may choose to limit the amount of tickets a single person may reserve.</p>
<h2>Change organisation name</h2>
<p>This should be self explanatory, but keep in mind that this change will only take effect after the next restart of the node app.</p>
</div>
</div>
<div id="footer"></div>
</body>
</html>