Skip to content

Commit 1b246f3

Browse files
remove abstracts (#753)
We no longer use abstracts in the docs.
1 parent b74d23f commit 1b246f3

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

61 files changed

+52
-273
lines changed

modules/ROOT/pages/administration/access-control/built-in-roles.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,7 @@
33
[[access-control-built-in-roles]]
44
= Built-in roles and privileges
55

6-
[abstract]
7-
--
8-
This section explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed.
9-
--
6+
This page explains the default privileges of the built-in roles in Neo4j and how to recreate them if needed.
107

118
All of the commands described in this chapter require that the user executing the commands has the rights to do so.
129
The privileges listed in the following sections are the default set of privileges for each built-in role:

modules/ROOT/pages/administration/access-control/database-administration.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,7 @@ CREATE USER jake SET PASSWORD 'abcd1234' CHANGE NOT REQUIRED;
1414
[[access-control-database-administration]]
1515
= Database administration
1616

17-
[abstract]
18-
--
19-
This section explains how to use Cypher to manage Neo4j database administrative privileges.
20-
--
17+
This page explains how to use Cypher to manage Neo4j database administrative privileges.
2118

2219
Administrators can use the following Cypher commands to manage Neo4j database administrative rights.
2320

modules/ROOT/pages/administration/access-control/dbms-administration.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,10 +64,7 @@ CREATE ROLE deniedConfigurationViewer IF NOT EXISTS;
6464
[[access-control-dbms-administration]]
6565
= DBMS administration
6666

67-
[abstract]
68-
--
69-
This section explains how to use Cypher to manage Neo4j DBMS administrative privileges.
70-
--
67+
This page explains how to use Cypher to manage Neo4j DBMS administrative privileges.
7168

7269
All DBMS privileges are relevant system-wide.
7370
Like user management, they do not belong to one specific database or graph.

modules/ROOT/pages/administration/access-control/limitations.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,10 +14,7 @@ CREATE ROLE free;
1414
[[access-control-limitations]]
1515
= Limitations
1616

17-
[abstract]
18-
--
19-
This section lists the known limitations and implications of Neo4js role-based access control security.
20-
--
17+
This page lists the known limitations and implications of Neo4j's role-based access control security.
2118

2219
[[access-control-limitations-indexes]]
2320
== Security and Indexes

modules/ROOT/pages/administration/access-control/manage-privileges.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,7 @@
44

55
= Managing privileges
66

7-
[abstract]
8-
--
9-
This section explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security.
10-
--
7+
This page explains how to use Cypher to manage privileges for Neo4j role-based access control and fine-grained security.
118

129
Privileges control the access rights to graph elements using a combined allowlist/denylist mechanism.
1310
It is possible to grant or deny access, or use a combination of the two.

modules/ROOT/pages/administration/access-control/manage-roles.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,7 @@ CREATE ROLE role2 IF NOT EXISTS;
1717
----
1818
////
1919

20-
[abstract]
21-
--
22-
This section explains how to use Cypher to manage roles in Neo4j.
23-
--
20+
This page explains how to use Cypher to manage roles in Neo4j.
2421

2522
Roles can be created and managed using a set of Cypher administration commands executed against the `system` database.
2623

modules/ROOT/pages/administration/access-control/manage-users.adoc

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,15 +3,11 @@
33
[[access-control-manage-users]]
44
= Managing users
55

6-
[abstract]
7-
--
8-
This section explains how to use Cypher to manage users in Neo4j.
9-
--
6+
This page explains how to use Cypher to manage users in Neo4j.
107

118
Users can be created and managed using a set of Cypher administration commands executed against the `system` database.
129
When connected to the DBMS over `bolt`, administration commands are automatically routed to the `system` database.
1310

14-
1511
[[access-control-user-syntax]]
1612
== User management command syntax
1713

modules/ROOT/pages/administration/access-control/privileges-reads.adoc

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,8 @@ CREATE ROLE regularUsers;
1111
[[access-control-privileges-reads]]
1212
= Read privileges
1313

14-
[abstract]
15-
--
16-
This section explains how to use Cypher to manage read privileges on graphs.
17-
--
14+
15+
This page explains how to use Cypher to manage read privileges on graphs.
1816

1917
There are three separate read privileges:
2018

modules/ROOT/pages/administration/access-control/privileges-writes.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,7 @@ CREATE ROLE regularUsers;
1111
[[access-control-privileges-writes]]
1212
= Write privileges
1313

14-
[abstract]
15-
--
16-
This section explains how to use Cypher to manage write privileges on graphs.
17-
--
14+
This page explains how to use Cypher to manage write privileges on graphs.
1815

1916
Write privileges are defined for different parts of the graph:
2017

modules/ROOT/pages/administration/aliases.adoc

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,7 @@
33
[[alias-management]]
44
= Database alias management
55

6-
[abstract]
7-
--
8-
This section explains how to use Cypher to manage database aliases in Neo4j.
9-
--
6+
This page explains how to use Cypher to manage database aliases in Neo4j.
107

118
There are two kinds of database aliases: local and remote.
129
A local database alias can only target a database within the same DBMS.

0 commit comments

Comments
 (0)