Q.01
Does the price change with the number of Teams?
MONJI+ bills monthly per Team.
You're charged for each Team on a paid plan — company, department, client, and so on.
About Teams & Projects
Learn the difference between “Teams” and “Projects” — the core units for managing your websites in MONJI+ —
plus how to set them up and how pricing, permissions, and security work.
plus how to set them up and how pricing, permissions, and security work.
What Are Teams
and Projects?
MONJI+ organizes WebOps around two units: Teams and Projects.
01 · TEAM
What is a Team
A company / organization
The outermost unit that subscribes to MONJI+.
Everything starts by creating a Team.
Manage member invitations, plans, and billing across the whole Team.
02 · PROJECT
What is a Project
One website
A per-site unit created inside a Team.
Create as many as you have sites.
This is where day-to-day WebOps happens — feedback, site checks, Wiki, and more.
Within one Team, create as many per-site Projects as you need.
Team
Team (company / organization)
Point
Team (company / organization)Members
…
…Projects
Project
Corporate site
Guests
…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
Project
E-commerce site
Guests
…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
Project
Careers site
Guests
…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
Project
Corporate site
Guests…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
Project
E-commerce site
Guests…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
Project
Careers site
Guests…
…FeedbackSite checkWikiGAChecklistFilesBookmarks
PointPoint
However many Projects you create in a Team, the monthly price is flat.
MONJI+ bills monthly per Team.
The price doesn't change with the number of Projects.
How Teams and Projects work —
in a short video
Organize info per site
and make WebOps easier
✕
Conventional WebOps
Feedback, files, and history are scattered, so who did what — and how far — is invisible.
- ✕Hard to tell which site info belongs to, so checks get missed
- ✕Unclear who's involved, so you hunt for the right contact
- ✕Feedback gets buried and tasks slip through
- ✕Info for unrelated sites gets shared too easily
- ✕Reviewing the history of past work takes time
Organize it with the Team / Project structure
WebOps with MONJI+
Organize the info, people, and history each site needs.
Reviewing, sharing, and handoffs go smoothly.
- Info is organized per site, so nothing's confusing
- Only the right people join, so it's easy to manage
- Feedback, files, and history stay together
- Manage access scope separately for each site
- Past history is easy to look back on
What Teams manage,
what Projects manage
Manage by company, department, or client with Teams;
organize per-site feedback, materials, history, and improvement info with Projects.
What you can do with a Team
Manage multiple sites and projects together
Invite internal members and external partners by role
See the progress of all Projects in the Team at a glance
Share common rules and operational info via the Team Wiki
Security settings such as IP address access restrictions- Manage your plan and payment method
A Team brings together your organization, contract, and members.
It's the foundation for operating across multiple sites.
What you can do with a Project
- Create and manage feedback for each site
Site check / Website Issue Detection- Build up per-site rules and knowledge in the Project Wiki
Share files like designs, materials, and images
Share related URLs and reference pages as bookmarks
Track site metrics with Google Analytics integration
Improve feedback quality with checklists
A Project brings together work, materials, and history.
Organizing by site prevents missed checks and mix-ups.
Choose how to set up your Teams
to fit how you operate
Manage everything easily in one Team, or split strictly by client.
Choose between two approaches based on your structure and security needs.
1
Keep everything in one Team
Keep all Projects in a single Team.
Internal members manage the whole Team, and clients join their assigned Projects as guests.
Recommended when you want to
- Operate your own sites all together
- Manage across sites with a small team
2
Split by client or department
Split into separate Teams for each client or department.
Each Team is independent, so you can keep information strictly separated.
* Each Team is billed separately.
Recommended when you want to
- Keep clients fully separated
- Have strict security requirements
How to get started
with Teams and Projects
Even first-timers can start WebOps in four steps.
1
STEP 01
Create a Team
Create a Team for your unit of operation — company, department, or client.
2
STEP 02
Create a Project
Create a Project inside the Team for each site you operate.
3
STEP 03
Invite members and guests
Invite internal members to the Team, and clients to each Project as guests.
4
STEP 04
Start WebOps
Run operations per site with feedback, site checks, Wiki, and more.
Common questions
before getting started
We've gathered the questions we hear most often about the number of Teams, pricing, inviting external members, and security.
Q.02
Does the price change with the number of Projects?
Because billing is per Team, the price doesn't change no matter how many Projects you create.
Within one Team, create as many Projects as you have sites.
Q.03
Can I invite people outside my company?
You can invite external people such as clients as guests, only to the Projects they need.
Since you can limit their scope, there's no worry of sharing unrelated info.
Q.04
Can I separate participants by Project?
Guests can be assigned to specific Projects.
Invite the clients or external partners in charge only to the Projects they need, so each site runs with just the people it needs.
*Members belong to the whole Team, so they can't be separated by Project.
Q.05
Can I manage multiple sites in one Project?
You can, but MONJI+ recommends one site per Project.
Splitting Projects by site makes feedback, files, history, and people easier to organize.
Conversely, bundling multiple sites into one Project tends to make information harder to tell apart, so take care.
Q.06
Is it secure?
You can separate access scope by Team and Project, limiting information to only the people involved.
On top of that, we provide security measures like two-step login authentication and IP-based access restrictions.
For details, see the security features page.
Start with one site.
Operate with Teams and Projects.
You don't have to use it on every site at once.
Start by creating a Project for a site where feedback tends to slip through.
Sites where feedback tends to be missed
Sites with many stakeholders and unclear contacts
Sites where external partners or clients are involved
Try all features free for 30 days.
Start your 30-day free trial
Experience all features for 30 days.
After that, core features stay free forever on the Free plan.