Member Management: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
(Created page with "= Member Management = == Overview == The Member Management feature in ACT 3 AI allows project owners and administrators to add, remove, and control access for team members. It ensures that everyone involved in a production has the right permissions to collaborate effectively while keeping sensitive content secure. == Key Benefits == 1. Centralized control over who can access and edit projects. 2. Assign roles with specific permissions to streamline workflows. 3. Secu...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
= Member Management =
== Overview ==
== Overview ==
The Member Management feature in ACT 3 AI allows project owners and administrators to add, remove, and control access for team members.   
The '''Member Management''' system in [[ACT3AI|ACT 3 AI]] lets organization admins add, remove, and manage users within their workspace.   
It ensures that everyone involved in a production has the right permissions to collaborate effectively while keeping sensitive content secure.
It ensures that roles, permissions, and project access are aligned with your team’s creative workflow.
 
== Key Benefits ==
1. Centralized control over who can access and edit projects.
2. Assign roles with specific permissions to streamline workflows.
3. Securely share assets, scripts, and project files with team members.
4. Easily onboard and offboard collaborators without disrupting production.
5. Maintain activity logs for accountability and version tracking.


== Workflow for Member Management ==
== 1. Purpose ==
1. **Access Member Management**   
* Enable collaborative video creation across teams 
  From the project dashboard, open the **Members** or **Team** tab.
* Control access to assets, [[Projects]], and [[Cloud_Storage_Management]] 
* Assign roles with tailored permissions  
* Track membership for billing and [[Subscription_Plan]] enforcement 


2. **Add New Members**  
== 2. Roles & Permissions ==
  Invite team members via email or link.  
* '''Owner:''' Full access to billing, credits, and all projects  
  * Assign a role during invitation.
* '''Admin:''' Manage members, assign roles, view [[Billing_Model]]  
  * Set project-level permissions.
* '''Creator:''' Create and edit [[Projects]], [[Scenes]], [[Timeline_&_Storyboard]] 
* '''Viewer:''' Read-only access to scripts, renders, and [[Build_Video]] outputs 


3. **Assign Roles & Permissions**   
== 3. Adding Members ==
  Common roles include:
# Go to **Organization → Members** in the [[Dashboard]]  
  * **Owner:** Full access, including billing and settings.
# Click **Invite Member** and enter email address 
  * **Admin:** Manage members, edit projects, and approve exports.
# Assign role (Owner, Admin, Creator, Viewer) 
  * **Editor:** Modify scenes, scripts, and assets.
# Invitation link is sent via email 
  * **Viewer:** Read-only access for review and feedback.


4. **Edit Member Permissions**   
== 4. Removing Members ==
  Update roles at any time to adjust access levels.
* Admins and Owners can remove members from the org 
* Removed members lose access to all [[Projects]] and [[Cloud_Storage_Management|stored assets]] 
* All edits remain preserved in version history  


5. **Remove Members**  
== 5. Project Access ==
  Revoke access for users who are no longer part of the project.
* Access is inherited from org membership 
* Specific projects can restrict editing to assigned members  
* [[Scenes]], [[Shots]], and [[Script_Editor]] edits are tracked by user ID 


6. **Monitor Activity**  
== 6. Billing & Limits ==
  View activity logs to see who made changes and when.
* [[Subscription_Plan]] defines number of included seats 
* Additional seats billed as overages  
* Role changes may affect billing tier recommendations 


== Permission Levels ==
== 7. Security ==
1. **Full Access** – Manage everything, including billing.
* RBAC (Role-Based Access Control) enforced 
2. **Edit Access** – Modify scripts, scenes, assets, and exports.
* Email verification required for new members 
3. **Comment Access** – Add notes and feedback without making changes.
* 2FA supported for Owners and Admins 
4. **View Access** – Read-only viewing of all project content.
* Audit logs of member changes viewable in org settings 


== Security Features ==
== 8. Roadmap ==
1. **Two-Factor Authentication (2FA):** Optional for secure logins.
* Granular project-level permissions 
2. **IP Restriction:** Limit access from specific IP ranges.
* Team groups with preset roles 
3. **Audit Logs:** Track edits, exports, and permission changes.
* Guest collaborators with temporary access


== Best Practices ==
----
1. Assign the minimum permissions necessary for each member’s role.
2. Regularly review the member list to remove inactive collaborators.
3. Use **Viewer** or **Commenter** roles for external reviewers.
4. Keep an activity log for large teams to maintain accountability.


== Related Pages ==
<small>See also: [[Organization]], [[Billing_Model]], [[Credit_System]], [[Subscription_Plan]], [[Dashboard]], [[Projects]]</small>
* [[Version_Control|Version Control]]
* [[Project_Structure|Project Structure]]
* [[Collaboration_and_Permissions|Collaboration & Permissions]]
* [[Build_Video|Rendering & Exporting Videos]]

Latest revision as of 08:13, 27 August 2025

Overview

The Member Management system in ACT 3 AI lets organization admins add, remove, and manage users within their workspace. It ensures that roles, permissions, and project access are aligned with your team’s creative workflow.

1. Purpose

2. Roles & Permissions

3. Adding Members

  1. Go to **Organization → Members** in the Dashboard
  2. Click **Invite Member** and enter email address
  3. Assign role (Owner, Admin, Creator, Viewer)
  4. Invitation link is sent via email

4. Removing Members

  • Admins and Owners can remove members from the org
  • Removed members lose access to all Projects and stored assets
  • All edits remain preserved in version history

5. Project Access

  • Access is inherited from org membership
  • Specific projects can restrict editing to assigned members
  • Scenes, Shots, and Script_Editor edits are tracked by user ID

6. Billing & Limits

  • Subscription_Plan defines number of included seats
  • Additional seats billed as overages
  • Role changes may affect billing tier recommendations

7. Security

  • RBAC (Role-Based Access Control) enforced
  • Email verification required for new members
  • 2FA supported for Owners and Admins
  • Audit logs of member changes viewable in org settings

8. Roadmap

  • Granular project-level permissions
  • Team groups with preset roles
  • Guest collaborators with temporary access

See also: Organization, Billing_Model, Credit_System, Subscription_Plan, Dashboard, Projects

Retrieved from "https://wiki.act3ai.com/index.php?title=Member_Management&oldid=613"