From 7de4383f0d7e5b3db8eb69e34795dec251ae842e Mon Sep 17 00:00:00 2001 From: M Date: Sun, 29 Nov 2015 17:33:50 -0500 Subject: * Moved sysconf default view modal content out to diffent view file --- app/view/sysconf/default.view.php | 23 +++-------------------- app/view/sysconf/user.modal.view.php | 30 ++++++++++++++++++++++++++++++ 2 files changed, 33 insertions(+), 20 deletions(-) create mode 100644 app/view/sysconf/user.modal.view.php (limited to 'app') diff --git a/app/view/sysconf/default.view.php b/app/view/sysconf/default.view.php index 74dfd79..a4dade9 100644 --- a/app/view/sysconf/default.view.php +++ b/app/view/sysconf/default.view.php @@ -19,29 +19,12 @@ - - - +

+ + diff --git a/app/view/sysconf/user.modal.view.php b/app/view/sysconf/user.modal.view.php new file mode 100644 index 0000000..b3650b0 --- /dev/null +++ b/app/view/sysconf/user.modal.view.php @@ -0,0 +1,30 @@ +
+
+
+
+ + + +
User Accounts
+ +
+ +
+
Scrott implements a very flexible permissions and access-control system. It all + starts with users' accounts. Users can create and maintain objects and share them + with other users if they choose. This is done with a mechanism similar to unix + file permission modes. Scrott objects form a hierarchy, so permissions from 'higher' + objects will cascade down. This means that a non-trusted user may control an issue + in your pad, but have no access to the pad itself.
+
+ +
+ +
+
+
+
-- cgit v1.2.3