{"id":5642,"date":"2026-06-04T02:59:40","date_gmt":"2026-06-04T02:59:40","guid":{"rendered":"https:\/\/www.cmsgalaxy.com\/blog\/?p=5642"},"modified":"2026-06-04T02:59:40","modified_gmt":"2026-06-04T02:59:40","slug":"moodle-cohorts-cohort-sync-and-course-meta-link-complete-guide-for-course-access-management","status":"publish","type":"post","link":"https:\/\/www.cmsgalaxy.com\/blog\/moodle-cohorts-cohort-sync-and-course-meta-link-complete-guide-for-course-access-management\/","title":{"rendered":"Moodle: Cohorts, Cohort Sync, and Course Meta Link \u2014 Complete Guide for Course Access Management"},"content":{"rendered":"\n
\n\n\n\n

1. What Is a Moodle Cohort?<\/h2>\n\n\n\n

A cohort<\/strong> in Moodle is a collection of users created at the site or category level. You can think of it as a central group of users that can be reused across many courses.<\/p>\n\n\n\n

Example cohorts:<\/p>\n\n\n\n

OneMembership\nDevOps Students\nSRE Premium Members\nCorporate Batch 2026\nAWS Training Learners\n<\/code><\/pre>\n\n\n\n
Moodle documentation explains that cohorts are different from course groups. A cohort exists for enrolment purposes across Moodle<\/strong>, while a group exists only inside a specific course<\/strong>. Cohorts can be brought into one or more courses in bulk. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Simple meaning:<\/p>\n\n\n\n
Cohort = Site\/category-level user group\nGroup = Course-level user group\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
OneMembership cohort\n    \u2193\nCourse 1\nCourse 2\nCourse 3\nCourse 4\n<\/code><\/pre>\n\n\n\n
If you add a user to the OneMembership<\/code> cohort, that user can automatically receive access to all courses where this cohort has been synced.<\/p>\n\n\n\n
\n\n\n\n
2. What Is Cohort Sync?<\/h2>\n\n\n\n
Cohort sync<\/strong> is an enrolment method. It automatically enrols members of a cohort into a course. If a user is added to the cohort, the user is enrolled in the course. If the user is removed from the cohort, the user can be unenrolled from the course depending on plugin settings. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Flow:<\/p>\n\n\n\n
User added to Cohort\n        \u2193\nCohort sync enrolment method\n        \u2193\nUser gets course access\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Cohort: OneMembership\nCourse: Docker Masterclass\nRole: Student\n<\/code><\/pre>\n\n\n\n
Once Cohort sync is added to the course, all users inside OneMembership<\/code> get access to Docker Masterclass<\/code>.<\/p>\n\n\n\n
\n\n\n\n
3. What Is Course Meta Link?<\/h2>\n\n\n\n
Course meta link<\/strong> is another enrolment method. It synchronises enrolments and roles from a source course<\/strong> to a target course<\/strong>. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Flow:<\/p>\n\n\n\n
Source Course users\n        \u2193\nCourse meta link\n        \u2193\nTarget Course access\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Source Course: DevOps Membership Course\nTarget Course: Kubernetes Course\n<\/code><\/pre>\n\n\n\n
If a student is enrolled in DevOps Membership Course<\/code>, Course meta link can automatically enrol that same student into Kubernetes Course<\/code>.<\/p>\n\n\n\n
This is useful when one course acts as the \u201cmain enrolment course\u201d and other courses depend on it.<\/p>\n\n\n\n
\n\n\n\n
4. Cohort Sync vs Course Meta Link<\/h2>\n\n\n\n
Feature<\/th>Cohort Sync<\/th>Course Meta Link<\/th><\/tr><\/thead>
Main source<\/td>Cohort<\/td>Another course<\/td><\/tr>
Best for<\/td>Memberships, batches, departments, customer groups<\/td>Linking enrolments between courses<\/td><\/tr>
Dependency<\/td>Depends on cohort<\/td>Depends on source course<\/td><\/tr>
Risk if source deleted<\/td>Cohort deletion may affect sync<\/td>Deleted source course can break linked enrolment references<\/td><\/tr>
Best scale usage<\/td>Very good for many courses<\/td>Useful, but can become messy at scale<\/td><\/tr>
Example<\/td>OneMembership \u2192 100 courses<\/td>Course A users \u2192 Course B access<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The most important difference:<\/p>\n\n\n\n
Cohort Sync = User group controls course access\nCourse Meta Link = Another course controls course access\n<\/code><\/pre>\n\n\n\n
For most membership-style platforms, training portals, corporate LMS sites, and paid access models, Cohort sync is usually cleaner<\/strong>.<\/p>\n\n\n\n
\n\n\n\n
5. When Should You Use Cohorts?<\/h2>\n\n\n\n
Use cohorts when you want to manage users centrally.<\/p>\n\n\n\n
Good use cases:<\/p>\n\n\n\n
One paid membership gives access to many courses\nOne corporate client has 500 learners\nOne training batch needs access to selected courses\nOne department needs access to internal learning modules\nOne subscription plan unlocks multiple courses\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Cohort: OneMembership\nCourses:\n- DevOps Foundation\n- Docker Training\n- Kubernetes Training\n- Jenkins Training\n- Terraform Training\n<\/code><\/pre>\n\n\n\n
Now instead of manually enrolling users in every course, you only manage users inside the cohort.<\/p>\n\n\n\n
This is the clean model:<\/p>\n\n\n\n
Add user to cohort once\n        \u2193\nUser gets access to all synced courses\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
6. When Should You Use Course Meta Link?<\/h2>\n\n\n\n
Use Course meta link when enrolment in one course should automatically give access to another course.<\/p>\n\n\n\n
Good use cases:<\/p>\n\n\n\n
A main course has child courses\nA program course controls access to module courses\nA master course enrolment should unlock supporting courses\nA certification path has linked sub-courses\n<\/code><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
Main Course: Full Stack Developer Program\nLinked Courses:\n- HTML Course\n- CSS Course\n- JavaScript Course\n- Laravel Course\n- React Course\n<\/code><\/pre>\n\n\n\n
The enrolment flow becomes:<\/p>\n\n\n\n
Student enrolled in Full Stack Developer Program\n        \u2193\nAutomatically enrolled in linked module courses\n<\/code><\/pre>\n\n\n\n
Course meta link can be useful, but it creates a dependency on the source course. If that source course is deleted or corrupted, target courses may have broken enrolment references.<\/p>\n\n\n\n
\n\n\n\n
7. Best Practice Recommendation<\/h2>\n\n\n\n
For your case, where you have a cohort like:<\/p>\n\n\n\n
OneMembership\n<\/code><\/pre>\n\n\n\n
and you want to assign access across many courses, the better structure is:<\/p>\n\n\n\n
OneMembership Cohort\n        \u2193\nCohort Sync\n        \u2193\nAll membership courses\n<\/code><\/pre>\n\n\n\n
Avoid using this unless you specifically need course-to-course dependency:<\/p>\n\n\n\n
Old Master Course\n        \u2193\nCourse Meta Link\n        \u2193\nOther Courses\n<\/code><\/pre>\n\n\n\n
For large Moodle systems with hundreds of courses, Cohort sync is easier to audit, easier to bulk update, and easier to explain to administrators.<\/p>\n\n\n\n
\n\n\n\n
Part 1: How to Create and Use Cohorts in Moodle<\/h1>\n\n\n\n
Step 1: Create a Cohort<\/h2>\n\n\n\n
Go to:<\/p>\n\n\n\n
Site administration \u2192 Users \u2192 Accounts \u2192 Cohorts\n<\/code><\/pre>\n\n\n\n
Click:<\/p>\n\n\n\n
Add new cohort\n<\/code><\/pre>\n\n\n\n
Add details:<\/p>\n\n\n\n
Name: OneMembership\nCohort ID: OneMembership\nContext: System\nVisible: Yes\n<\/code><\/pre>\n\n\n\n
Moodle allows cohorts to be created at the system level or within a course category. A system cohort is available site-wide, while a category cohort is available within that category context. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Important: Always set a clear Cohort ID<\/strong>. Moodle upload tools often use the cohort ID, not only the cohort display name. Moodle documentation warns that upload files work on the cohort ID, not the cohort name. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Good naming:<\/p>\n\n\n\n
Cohort name: OneMembership\nCohort ID: OneMembership\n<\/code><\/pre>\n\n\n\n
Avoid blank IDs.<\/p>\n\n\n\n
\n\n\n\n
Step 2: Add Users to a Cohort<\/h2>\n\n\n\n
You can add users manually:<\/p>\n\n\n\n
Site administration \u2192 Users \u2192 Accounts \u2192 Cohorts\n<\/code><\/pre>\n\n\n\n
Then click the members icon and add users.<\/p>\n\n\n\n
For bulk assignment, Moodle supports adding users to cohorts using upload users CSV. The upload format can include fields such as username<\/code> and cohort1<\/code>. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Example CSV:<\/p>\n\n\n\n
username,cohort1\nrajesh,OneMembership\namit,OneMembership\npriya,OneMembership\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Step 3: Enable Cohort Sync Plugin<\/h2>\n\n\n\n
Go to:<\/p>\n\n\n\n
Site administration \u2192 Plugins \u2192 Enrolments \u2192 Manage enrol plugins\n<\/code><\/pre>\n\n\n\n
Enable:<\/p>\n\n\n\n
Cohort sync\n<\/code><\/pre>\n\n\n\n
Moodle documentation says Cohort sync must be enabled by an administrator before it can be used in courses. (Moodle Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
Step 4: Add Cohort Sync to a Course<\/h2>\n\n\n\n
Open the course:<\/p>\n\n\n\n
Course \u2192 Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
Choose:<\/p>\n\n\n\n
Add method \u2192 Cohort sync\n<\/code><\/pre>\n\n\n\n
Select:<\/p>\n\n\n\n
Cohort: OneMembership\nRole: Student\n<\/code><\/pre>\n\n\n\n
Click:<\/p>\n\n\n\n
Add method\n<\/code><\/pre>\n\n\n\n
Now all users in OneMembership<\/code> will be enrolled into that course.<\/p>\n\n\n\n
\n\n\n\n
Part 2: How to Add One Cohort to Hundreds of Courses<\/h1>\n\n\n\n
If you have hundreds of courses, do not add Cohort sync one by one manually.<\/p>\n\n\n\n
Use Moodle\u2019s Upload courses<\/strong> tool.<\/p>\n\n\n\n
Moodle\u2019s Upload courses tool allows administrators or users with the correct capability to create\/update courses using CSV, and it supports course enrolment fields. (Moodle Docs<\/a>)<\/p>\n\n\n\n
Go to:<\/p>\n\n\n\n
Site administration \u2192 Courses \u2192 Upload courses\n<\/code><\/pre>\n\n\n\n
Use a CSV like this:<\/p>\n\n\n\n
shortname,enrolment_1,enrolment_1_cohortidnumber,enrolment_1_role\nDEVOPS101,cohort,OneMembership,student\nDOCKER101,cohort,OneMembership,student\nK8S101,cohort,OneMembership,student\nJENKINS101,cohort,OneMembership,student\n<\/code><\/pre>\n\n\n\n
Recommended upload options:<\/p>\n\n\n\n
Upload mode: Update existing courses only\nUpdate mode: Update with CSV data\nPreview: Yes\n<\/code><\/pre>\n\n\n\n
This is the best Moodle-native way to add one cohort to many existing courses.<\/p>\n\n\n\n
\n\n\n\n
Part 3: Course Meta Link Setup<\/h1>\n\n\n\n
Step 1: Enable Course Meta Link Plugin<\/h2>\n\n\n\n
Go to:<\/p>\n\n\n\n
Site administration \u2192 Plugins \u2192 Enrolments \u2192 Manage enrol plugins\n<\/code><\/pre>\n\n\n\n
Enable:<\/p>\n\n\n\n
Course meta link\n<\/code><\/pre>\n\n\n\n
Moodle documentation says Course meta link must be enabled in enrolment plugin settings before use. (Moodle Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
Step 2: Add Course Meta Link to a Target Course<\/h2>\n\n\n\n
Open the target course:<\/p>\n\n\n\n
Course \u2192 Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
Choose:<\/p>\n\n\n\n
Add method \u2192 Course meta link\n<\/code><\/pre>\n\n\n\n
Then select the source course.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
Source Course: DevOps Membership Course\nTarget Course: Kubernetes Course\n<\/code><\/pre>\n\n\n\n
Now users enrolled in the source course are synchronised into the target course.<\/p>\n\n\n\n
Moodle documentation notes that Course meta link synchronises enrolments and roles from source course to target course; by default, role assignments from the source course are synchronised unless roles are excluded in plugin settings. (Moodle Docs<\/a>)<\/p>\n\n\n\n
\n\n\n\n
Part 4: Common Mistake \u2014 Using Course Meta Link Like a Membership System<\/h1>\n\n\n\n
Many Moodle admins create a \u201cmaster course\u201d and link all other courses to it:<\/p>\n\n\n\n
Master Course\n    \u2193\nCourse 1\nCourse 2\nCourse 3\nCourse 4\n<\/code><\/pre>\n\n\n\n
This works, but it is not always the best design.<\/p>\n\n\n\n
If the master course is deleted, hidden incorrectly, restored badly, or corrupted, linked target courses may have broken enrolment references.<\/p>\n\n\n\n
Better design for membership:<\/p>\n\n\n\n
OneMembership Cohort\n    \u2193\nCourse 1\nCourse 2\nCourse 3\nCourse 4\n<\/code><\/pre>\n\n\n\n
This is simpler because the cohort is the access control object, not a course.<\/p>\n\n\n\n
\n\n\n\n
Part 5: Troubleshooting \u201cCan\u2019t Find Data Record in Database\u201d<\/h1>\n\n\n\n
If you deleted old source\/master courses and then some courses show this error:<\/p>\n\n\n\n
Can't find data record in database.\n<\/code><\/pre>\n\n\n\n
when opening:<\/p>\n\n\n\n
Participants \u2192 Enrolment methods\n<\/code><\/pre>\n\n\n\n
then the likely cause is a broken Course meta link enrolment record.<\/p>\n\n\n\n
Moodle is trying to load an old linked source course, but that course no longer exists.<\/p>\n\n\n\n
SQL: Find Broken Course Meta Links<\/h2>\n\n\n\n
SELECT \n    e.id AS enrol_instance_id,\n    e.courseid AS target_course_id,\n    target.shortname AS target_shortname,\n    target.fullname AS target_course_name,\n    e.customint1 AS missing_source_course_id\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nLEFT JOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta'\nAND source.id IS NULL;\n<\/code><\/pre>\n\n\n\n
Meaning:<\/p>\n\n\n\n
target_course_id = course where enrolment page may be broken\nmissing_source_course_id = deleted course previously used as source\n<\/code><\/pre>\n\n\n\n
Before fixing anything, take a database backup.<\/p>\n\n\n\n
mysqldump -u DBUSER -p DBNAME > moodle_before_fix_broken_meta_links.sql\n<\/code><\/pre>\n\n\n\n
Then remove broken enrolment instances using Moodle\u2019s API, not direct SQL deletion.<\/p>\n\n\n\n
\n\n\n\n
Part 6: Useful SQL Reports for Moodle Cohorts and Meta Links<\/h1>\n\n\n\n
1. Find Courses Where OneMembership<\/code> Is Already Added<\/h2>\n\n\n\n
SELECT \n    c.id AS course_id,\n    c.shortname,\n    c.fullname,\n    cc.name AS category_name,\n    e.id AS enrol_instance_id,\n    e.status\nFROM mdl_course c\nJOIN mdl_enrol e \n     ON e.courseid = c.id\nJOIN mdl_cohort ch \n     ON ch.id = e.customint1\nLEFT JOIN mdl_course_categories cc \n     ON cc.id = c.category\nWHERE e.enrol = 'cohort'\nAND (\n    ch.name = 'OneMembership'\n    OR ch.idnumber = 'OneMembership'\n)\nORDER BY cc.name, c.shortname;\n<\/code><\/pre>\n\n\n\n
2. Find Courses Where OneMembership<\/code> Is Not Added<\/h2>\n\n\n\n
SELECT \n    c.id AS course_id,\n    c.shortname,\n    c.fullname,\n    cc.name AS category_name\nFROM mdl_course c\nLEFT JOIN mdl_course_categories cc \n       ON cc.id = c.category\nWHERE c.id <> 1\nAND NOT EXISTS (\n    SELECT 1\n    FROM mdl_enrol e\n    JOIN mdl_cohort ch \n         ON ch.id = e.customint1\n    WHERE e.courseid = c.id\n      AND e.enrol = 'cohort'\n      AND (\n          ch.name = 'OneMembership'\n          OR ch.idnumber = 'OneMembership'\n      )\n)\nORDER BY cc.name, c.shortname;\n<\/code><\/pre>\n\n\n\n
3. Find Course Meta Links<\/h2>\n\n\n\n
SELECT \n    e.id AS enrol_instance_id,\n    target.id AS target_course_id,\n    target.shortname AS target_course_shortname,\n    target.fullname AS target_course_name,\n    source.id AS source_course_id,\n    source.shortname AS source_course_shortname,\n    source.fullname AS source_course_name\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nJOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta'\nORDER BY source.fullname, target.fullname;\n<\/code><\/pre>\n\n\n\n
4. Find Duplicate-Looking Course Names by First 4 Characters<\/h2>\n\n\n\n
SELECT \n    LEFT(REGEXP_REPLACE(LOWER(TRIM(c.fullname)), '[^a-z0-9]', ''), 4) AS first_4_normalized_chars,\n    COUNT(*) AS total_courses,\n    GROUP_CONCAT(c.id ORDER BY c.id SEPARATOR ' | ') AS course_ids,\n    GROUP_CONCAT(c.shortname ORDER BY c.id SEPARATOR ' | ') AS shortnames,\n    GROUP_CONCAT(c.fullname ORDER BY c.id SEPARATOR ' | ') AS course_names\nFROM mdl_course c\nWHERE c.id <> 1\nGROUP BY LEFT(REGEXP_REPLACE(LOWER(TRIM(c.fullname)), '[^a-z0-9]', ''), 4)\nHAVING COUNT(*) > 1\nORDER BY total_courses DESC, first_4_normalized_chars;\n<\/code><\/pre>\n\n\n\n
This helps find courses that may have naming convention differences.<\/p>\n\n\n\n
Example:<\/p>\n\n\n\n
DevOps Basics\nDevOps Basic Course\nDevOps Basics 2025\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Part 7: Migration Plan from Course Meta Link to Cohort Sync<\/h1>\n\n\n\n
If your Moodle site currently uses Course meta links but you want to move to Cohort sync, use this plan.<\/p>\n\n\n\n
Step 1: Audit Existing Meta Links<\/h2>\n\n\n\n
Run:<\/p>\n\n\n\n
SELECT \n    e.id AS enrol_instance_id,\n    target.id AS target_course_id,\n    target.fullname AS target_course_name,\n    source.id AS source_course_id,\n    source.fullname AS source_course_name\nFROM mdl_enrol e\nJOIN mdl_course target ON target.id = e.courseid\nJOIN mdl_course source ON source.id = e.customint1\nWHERE e.enrol = 'meta'\nORDER BY source.fullname, target.fullname;\n<\/code><\/pre>\n\n\n\n
Step 2: Create Replacement Cohort<\/h2>\n\n\n\n
Create:<\/p>\n\n\n\n
OneMembership\n<\/code><\/pre>\n\n\n\n
Step 3: Add Existing Users to Cohort<\/h2>\n\n\n\n
Either manually add users or upload users using CSV:<\/p>\n\n\n\n
username,cohort1\nstudent1,OneMembership\nstudent2,OneMembership\nstudent3,OneMembership\n<\/code><\/pre>\n\n\n\n
Step 4: Add Cohort Sync to Target Courses<\/h2>\n\n\n\n
Use Upload courses CSV:<\/p>\n\n\n\n
shortname,enrolment_1,enrolment_1_cohortidnumber,enrolment_1_role\nCOURSE001,cohort,OneMembership,student\nCOURSE002,cohort,OneMembership,student\nCOURSE003,cohort,OneMembership,student\n<\/code><\/pre>\n\n\n\n
Step 5: Verify Access<\/h2>\n\n\n\n
Check one student account:<\/p>\n\n\n\n
User is in OneMembership cohort\nUser can access all required courses\n<\/code><\/pre>\n\n\n\n
Step 6: Remove Old Course Meta Links<\/h2>\n\n\n\n
After confirming Cohort sync is working, remove old Course meta link enrolment methods from the affected courses.<\/p>\n\n\n\n
Do not delete source courses until you confirm no course still depends on them.<\/p>\n\n\n\n
\n\n\n\n
Part 8: Which One Should You Use?<\/h1>\n\n\n\n
Use Cohort Sync When:<\/h2>\n\n\n\n
You sell memberships\nYou manage corporate learners\nYou have batches of students\nYou want one group to access many courses\nYou want cleaner long-term access control\nYou want to bulk manage hundreds of courses\n<\/code><\/pre>\n\n\n\n
Use Course Meta Link When:<\/h2>\n\n\n\n
One course genuinely controls another course\nA program course should unlock module courses\nA parent course and child courses are intentionally connected\nYou want enrolment and role sync from one course to another\n<\/code><\/pre>\n\n\n\n
Avoid Course Meta Link When:<\/h2>\n\n\n\n
You only need membership-based course access\nYou are using a dummy\/master course just as a user container\nYou plan to delete or frequently modify source courses\nYou have hundreds of courses and need simple access control\n<\/code><\/pre>\n\n\n\n
\n\n\n\n
Final Architecture Recommendation<\/h1>\n\n\n\n
For a Moodle business, training company, certification platform, or membership portal, the clean structure is:<\/p>\n\n\n\n
Users\n  \u2193\nCohort: OneMembership\n  \u2193\nCohort Sync\n  \u2193\nCourses\n<\/code><\/pre>\n\n\n\n
For example:<\/p>\n\n\n\n
OneMembership\n  \u251c\u2500\u2500 DevOps Foundation\n  \u251c\u2500\u2500 Docker Masterclass\n  \u251c\u2500\u2500 Kubernetes Advanced\n  \u251c\u2500\u2500 Jenkins CI\/CD\n  \u251c\u2500\u2500 Terraform on AWS\n  \u2514\u2500\u2500 SRE Foundation\n<\/code><\/pre>\n\n\n\n
This gives you one central access point. Add user once, remove user once, and Moodle handles access through Cohort sync.<\/p>\n\n\n\n
Course meta link is powerful, but use it only when courses are logically dependent on each other.<\/p>\n\n\n\n
The simplest rule is:<\/p>\n\n\n\n
For user groups, use Cohorts.\nFor course-to-course dependency, use Course meta link.\n<\/code><\/pre>\n\n\n\n
That one rule will save you many Moodle admin headaches.<\/p>\n","protected":false},"excerpt":{"rendered":"
1. What Is a Moodle Cohort? A cohort in Moodle is a collection of users created at the site or category level. You can think of it… <\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5642","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5642","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/comments?post=5642"}],"version-history":[{"count":1,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5642\/revisions"}],"predecessor-version":[{"id":5643,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/posts\/5642\/revisions\/5643"}],"wp:attachment":[{"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/media?parent=5642"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/categories?post=5642"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmsgalaxy.com\/blog\/wp-json\/wp\/v2\/tags?post=5642"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}