TeamCloud

Work together. Ship only what's approved.

TeamCloud connects Lucy Studio, versions and deployment in one project, so your team works together and only approved screen updates reach users.

01

Nothing reaches users
until it's approved.

Request

Editors ask to deploy.
Nothing ships on its own.

When a screen update is ready, a Project Editor sends a deploy request. The request carries the version, its commit and who made it, so the reviewer knows exactly what is about to go out.

Project Editors deploy to Test on their own and request a move to Stage or Production. A Project Manager or an Org admin approves the request. When they promote a version themselves, it is approved automatically.

/Northgate/northgate_opsMP

Deploy

northgate_ops
Stage → ProdPending approval
v1.5 · hourly chart as line
Requested by JiwonEditor · 5 min ago · 3f2a81d
ApproveReject
Production current deployment
VERSION · BRANCHv1.4 · main
STATUSSucceeded
DEPLOYED BYMinji · 2 days ago
History
  • v1.4alerts listMinji · 2 days ago
  • v1.2hourly chartMinji · 3 weeks ago
Approve

One approval.
The same build goes live.

The version you tested is the version that ships. Approve it and it moves from Stage to Production as it is, with nothing rebuilt per environment.

Anyone who can approve deploys can revoke a release from an environment. Each environment keeps its own deploy history.

/Northgate/northgate_opsMP
← Stage

v1.5

SucceededStage deployment
TestSucceeded
StageCurrent
Prodv1.4 live
Promote the same build, nothing is rebuilt
Deployment
BRANCHfeature/hourly-chart
PROMOTED FROMTest
DEPLOYED BYJiwon · 20 min ago
Commits
  • 3f2a81dSwitch the hourly chart to a lineJiwon
02

One organization.
Run by your admins.

Org Owners and Org Admins decide who joins, how people are grouped and who can change the organization.

Members

Invite people and give each a role.

Invite members by email, change their roles, and remove access when someone leaves.

/NorthgateMP

Members

24 members · 2 pending
SH
Seojin Hanseojin@northgate.com
Org Member
Org AdminManages members, teams and settings
Org MemberSees members, projects and teams
Remove from organization
  • MPMinji ParkOrg Owner
  • JLJiwon LeeOrg Admin
  • —daniel@northgate.comInvitation sent
Teams

Group people into teams.

Each team has a Team Manager who adds and removes its members.

/NorthgateMP

Teams

5 teams
App developers8 members
Edit team
  • JLJiwon LeeTeam Manager
  • SHSeojin HanTeam Member
  • DKDaniel KimTeam Member
  • 4Designers4 members
  • 6QA6 members
Settings

Organization changes stay with admins.

Only Org Owners and Org Admins change organization settings and view the audit log. Deleting the organization or transferring ownership is for the Org Owner alone.

Organization roles at a glanceSample from the default role templates
What you can doOrg OwnerOrg AdminOrg Member
See members, projects and teams✓✓✓
Invite and remove members, change their roles✓✓—
Delete the organization or transfer ownership✓——
Change organization settings and view the audit log✓✓—
Every project and team permission✓✓—
Create projects and teams✓✓—
Manage service accounts and tokens✓✓—
See all permissions in the manual ↗
03

Same project for everyone.
Controls that fit each role.

Managers run the project.

A Project Manager edits, approves deploys and decides who joins.

Editors build and ask.

A Project Editor changes screens and tests them, then asks for approval before anything moves closer to users.

Viewers follow along.

A Project Viewer sees the project and its history without changing anything.

Project roles at a glanceSample from the default role templates
What you can doProject ManagerProject EditorProject Viewer
View the project and deploy history✓✓✓
Edit screens and push changes✓✓—
Deploy to Test✓✓—
Move to Stage or Prod✓Request—
Approve, reject or revoke a deploy✓——
Add members and change their roles✓——
Change project settings✓——
Force-release file locks✓——
See all permissions in the manual ↗

Org Owners and Org Admins have every project permission. Teams can be given a project role, and permissions from every path add up.

04

Every change
is a version.

Your team always continues from the same baseline, and you can see who changed what.

History

Each save is kept as a version.

Every version shows its tag, commit, author and message, so the history reads like a log of your app.

Continue

Pick up where a teammate left off.

Open a teammate's version, review what changed, then carry the work forward from there.

/Northgate/northgate_opsMP
← Versions

v1.5

hourly chart as line
AUTHORJiwon · Editor
COMMIT3f2a81d
SAVED3 hours ago
Switch the hourly chart to a line
Open it in Lucy Studio and keep working
Changed screens
  • 2dashboard · hourly_chart+48 −12
  • 1dashboard · legend+6 −2
/Northgate/northgate_opsMP

Settings

Organization · Northgate
Where TeamCloud runs
CloudOn-Premises
TeamCloud address
teamcloud.northgate.internal
DATA STORED ONYour servers
AUDIT LOGEvery version and deploy
Members
MEMBERS24
TEAMS5
PROJECTS12
05

Runs inside your network.
Your rules stay in place.

Q.

Where does our data live?

With On-Premises Enterprise, TeamCloud runs on your own servers, so projects, versions and deploy history stay inside your network.

Q.

Cloud or on-premises?

Choose Cloud Enterprise, hosted by Edencrew, or On-Premises Enterprise, run under your policy. Roles, approvals and versions work the same in both.

Q.

Can we see who changed what?

Every version records its tag, commit, author and message, and every environment keeps its deploy history.

Ship with confidence.

Your team collaborates on versions, and only approved screen updates reach your users.