5 Commits (a2d250412eb9e4d603721b43f151bf85254bb3bc)

Author	SHA1	Message	Date
Marcelo Schmidt	ca4741192a	Fixes #2346; Adds administration menu when 'manage-integrations' permission is added.	10 years ago
Marcelo Schmidt	3eb4ed97de	Change admin statistics for admin info.	10 years ago
Rafael Caferati	d70c4e2ee6	rocketchat-ui initial implementation	10 years ago
Marcelo Schmidt	3da68fdd27	Initial commit	10 years ago
Rodrigo Nascimento	22a1dbdfde	Render the name of setting group in menu using the id if the i18nLabel does not exists	10 years ago
Aaron Ogle	769f4fa42c	Import framework started.	10 years ago
Reid Wakida	c2e6e0fa2c	Create RocketChat authorization package that handles role and permission ... based authorization Leverages alanning:roles package to associate a user to a role. Uses alanning:roles optional "group" parameter to limit the role's scope to either the global level or room level. The global level is applicable to users that can perform administrative functions. The room level is applicable to users that can perform room specific administrative functions (like a moderator). A role can have zero or more permissions. Permissions and their association to roles are defined by this package Authorization checks are based on whether or not the user has a role or permission. The roles, permissions, and their association are statically defined at this time. Eventually, there should be an API to dynamically create a role and associate it to static permission(s). Old 'isAdmin' and '.admin is true' checks have been replaced with corresponding hasPermission authorization checks. Additionally, code that automatically assigned admin privileges are updated to assign 'admin' role instead. channel/direct message/private group code checks authorization to edit properties (e.g. title) and edit/delete messages (regardless of the system level allow edit/delete settings). - user with 'admin' role are authorized to do anything - room creator is assigned 'moderator' role that can edit the room and edit/delete messages - members can only edit/delete their own messages IF system wide settings permit them to. v19 migration will - add 'admin' role to users with admin:true property - add 'moderator' role scoped to room for room creators - add 'user' role to all users. There are known issues unrelated to the changes made - If a user with edit/delete message room permissions logs out then a user without edit/delete message room permissions logs in, then they will see edit/delete icons. The server will deny execution - edit/delete icons are not reactive Thus if the system level allow edit/delete message setting is toggled, the icons will not reflect it. The server will deny execution.	10 years ago
Marcelo Schmidt	9a610329f1	Administration / Rooms	11 years ago
Marcelo Schmidt	3464f07235	Admin settings separation	11 years ago
Marcelo Schmidt	9ef80f6266	Replaced /settings for /admin	11 years ago