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
Line 2: Line 2:


== 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. Purpose ==
1. Centralized control over who can access and edit projects.
* Enable collaborative video creation across teams 
2. Assign roles with specific permissions to streamline workflows.
* Control access to assets, [[Projects]], and [[Cloud_Storage_Management]] 
3. Securely share assets, scripts, and project files with team members.
* Assign roles with tailored permissions
4. Easily onboard and offboard collaborators without disrupting production.
* Track membership for billing and [[Subscription_Plan]] enforcement 
5. Maintain activity logs for accountability and version tracking.


== Workflow for Member Management ==
== 2. Roles & Permissions ==
1. **Access Member Management**   
* '''Owner:''' Full access to billing, credits, and all projects 
  From the project dashboard, open the **Members** or **Team** tab.
* '''Admin:''' Manage members, assign roles, view [[Billing_Model]] 
* '''Creator:''' Create and edit [[Projects]], [[Scenes]], [[Timeline_&_Storyboard]]  
* '''Viewer:''' Read-only access to scripts, renders, and [[Build_Video]] outputs 


2. **Add New Members**   
== 3. Adding Members ==
  Invite team members via email or link.  
# Go to **Organization → Members** in the [[Dashboard]]  
  * Assign a role during invitation.
# Click **Invite Member** and enter email address  
  * Set project-level permissions.
# Assign role (Owner, Admin, Creator, Viewer) 
# Invitation link is sent via email 


3. **Assign Roles & Permissions** 
== 4. Removing Members ==
  Common roles include:
* Admins and Owners can remove members from the org 
  * **Owner:** Full access, including billing and settings.
* Removed members lose access to all [[Projects]] and [[Cloud_Storage_Management|stored assets]] 
  * **Admin:** Manage members, edit projects, and approve exports.
* All edits remain preserved in version history 
  * **Editor:** Modify scenes, scripts, and assets.
  * **Viewer:** Read-only access for review and feedback.


4. **Edit Member Permissions**   
== 5. Project Access ==
  Update roles at any time to adjust access levels.
* 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  


5. **Remove Members**   
== 6. Billing & Limits ==
  Revoke access for users who are no longer part of the project.
* [[Subscription_Plan]] defines number of included seats 
* Additional seats billed as overages 
* Role changes may affect billing tier recommendations  


6. **Monitor Activity**   
== 7. Security ==
  View activity logs to see who made changes and when.
* 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 


== Permission Levels ==
== 8. Roadmap ==
1. **Full Access** – Manage everything, including billing.
* Granular project-level permissions 
2. **Edit Access** – Modify scripts, scenes, assets, and exports.
* Team groups with preset roles 
3. **Comment Access** – Add notes and feedback without making changes.
* Guest collaborators with temporary access 
4. **View Access** – Read-only viewing of all project content.


== Security Features ==
----
1. **Two-Factor Authentication (2FA):** Optional for secure logins.
2. **IP Restriction:** Limit access from specific IP ranges.
3. **Audit Logs:** Track edits, exports, and permission changes.


== Best Practices ==
<small>See also: [[Organization]], [[Billing_Model]], [[Credit_System]], [[Subscription_Plan]], [[Dashboard]], [[Projects]]</small>
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 ==
* [[Version_Control|Version Control]]
* [[Project_Structure|Project Structure]]
* [[Collaboration_and_Permissions|Collaboration & Permissions]]
* [[Build_Video|Rendering & Exporting Videos]]

Revision as of 10:41, 20 August 2025

Member Management

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