Show theme settings Shopping cart Download trialFree Trial
Change Theme Settings
Change Theme Settings
Themes
 
Show All Themes
v
...v

Document Protection

H
AA
UN
RE
AB
V
X
C
ZF
FN
FF
FS
FG
FK
7
1
2
3
4
5
6
FC
I
E
ZP
PG
U
N
M
AO
AI
8
AL
AC
AR
AJ
K
H
ZS
L
ZE
FD
R
SA
N
ZP
B
ZT
T
ZI
P
ZL
K
I
ZH
H
O
PN
PC
TE
X
ZS
U
P
ZS
SP
M
O
SZ
J
B
ZB
PC
RE
TO
T
UP
A
CA
IN
IS
UD
M
ZI
CF
I
ZM
P
FC
FR
U
ZP
Q
M
X
V
ZF
F
W
DV
L
P
ZS
R
ZV
F
JT
ZO
A
T
R
M
N
U
ZS
S
ZB
O
L
W
C
B
H
JL
ZT
K
TG
O
ZR
I
D
A
BE
L
R
ZM
M
P
ZC
BA
F
ZA
TL
TC
TR
CL
CC
CR
BL
BC
BR
N
JH
ZN
E
G
R
X
K
ZO
A
V
ZP
HO
FO
ZC
C
JD
B
SH
SA
W
C
D
TW
P
AF
AE
  • Undopo
    Undo
  • Cut
    Clipboardpo
    Clipboard
  • v
    v
    po
    po
    po
    Fontpo
    dialogboxlauncherFont
  • po
    po
    Paragraphpo
    dialogboxlauncherParagraph
  • Stylespo
    Styles
  • Editing
  • Table Style Optionspo
    Table Style Options
  • Table Stylespo
    Table Styles
  • v
    v
    Borders & Shadingspo
    dialogboxlauncherBorders & Shadings
  • Navigation
  • Options
  • Header from Top:
    +
    -
    Footer from Bottom:
    +
    -
    Positionpo
    Position
  • Close
  • v
    Shape Stylespo
    Shape Styles
  • dialogboxlauncherArrange
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Team Operating Agreement 
 
 
 
 
 
lawyer@somecompan
y.com 
projectmanager@somecomp
any.com 
senior@somecompan
y.com 
novice@somecompa
ny.com 
 
Purpose of the Team Operating Agreement (TOA) 
This  TOA  serves  as  the  guidelines  and  ground  rules  to  help  the  project  team  work  most 
productively  together  over  the  course  of  the  project.  The  TOA  is  a  living  document  and 
may  be  updated  as  the  need  arises  throughout  the  project.  Any  updates  will  be  discussed 
with and ratified by the project team members. 
 
Team Communications 
    The  project’s  site  will  house  the  most  up-to-date  version  of  project  documents.  All 
team members will be given access. 
    Meeting  agendas  will  be  e-mailed  to  project  team  members  at  least  24  hours 
prior to meetings. 
    Team  members  will  appreciate  the  sensitive  nature  of  information  discussed 
during  this  project  and  will  share  with  care.  Where  applicable,  documents  will 
include a footer indicating that information is confidential. 
    “Sidebar”  conversations  between  team  members  during  team  meetings  will  not 
be allowed. 
    All communication will be open and courteous. No “overtalking” or interrupting. 
     Team members will keep each other informed. 
 
Decision Making 
    Consensus  means  that  everyone  can  live  with  the  decision.  It  doesn’t  mean 
everyone has to agree 100%. 
    The  team  will  use  thumbs  up/thumbs  down  voting  to  make  decisions  quickly  and 
move on. 
1.   Thumbs up = agree with no further discussion. 
2.   Thumbs  sideways  =  agree,  but  have  further  questions.  (Questions  will  be 
asked and answered immediately after the vote.) 
3.   Thumbs  down  =  cannot  agree  to  the  solution  proposed.  (Be  prepared  to 
answer  the  question:  What  would  it  take  for  you  to  go  to  thumbs  sideways 
or thumbs up?) 
    Anyone on the team may call for a vote at any time. 
    Members may abstain from voting. 
    No decision is made if there are any thumbs-down votes. 
     Meeting  minutes  will  document  the  decisions  made.  If  you  have  questions  after 
reviewing  the  minutes,  contact  the  project  manager  and  determine  the  course  of 
action, such as to bring questions to the team for discussion again. 
 
Meetings 
Project  team  members  will  meet  twice  a  month.  During  each  meeting,  a  “parking  lot” 
will be used to record topics that require discussion at a later date. 
Issues,  risks,  change  requests,  and  action  items  will  be  reviewed  and  updated  at  each 
meeting. 
The  project  manager  will  be  responsible  for  facilitating  and  keeping  meetings  on  track. 
Team  members  will  accept  the  project  manager’s  decision  to  table  or  “park”  a  discussion 
topic. 
Meetings  will  start  and  end  on  time.  Team  members  will  attend  meetings  in  person  when 
feasible. A dial-in number will be available for remote attendance. 
It   is   the   responsibility   of   each   team   member   to   stay   current   on   the   project   team 
activities, even when he or she has missed a meeting 
 
Personal Courtesies 
Each   team   member   represents   a   specific   area   of   expertise   or   business   unit.   Team 
members  will  bring  their  individual  perspectives  to  the  team  and  will  also  consider  what 
is best for the company. 
All  cell  phones  and  other  communication  devices  must  be  silenced  during  meetings  and 
used on an exception basis only 
 
 
PROJECT COMMUNICATION PLAN 
CONFIDENTIAL                                           PAGE 2                                               TUESDAY, 
FEBRUARY 11, 2025 
Reviewed and approved by: 
Project Manager 
 
Senior Team Member 
 
Novice Team Member 
 
Company Lawyer 
 
 
PROJECT COMMUNICATION PLAN 
CONFIDENTIAL                                           PAGE 3                                               TUESDAY, 
FEBRUARY 11, 2025 
Authentication
v
Range Permissions
v
v
Did this demo address your needs?
If you’d like us to extend this demo further, please describe your needs below.
Thank you in advance for your cooperation.
SEND FEEDBACK

The ASP.NET Rich Text Editor (ASPxRichEdit) provides support for working with protected documents. When the RichEdit opens a fully protected document, users cannot edit it. If a protected document includes range permissions that enable editing document parts for a unique user or user group, the RichEdit is able to identify the current user and grant him/her the corresponding permissions. Use the RichEdit's Authentication property to authorize the current document user by its name, email or user group name. You can also define how the permitted ranges are highlighted within the RichEdit by using the RangePermission property.

In this demo, the RichEdit opens a protected document that includes permitted ranges for four users identified by email: each user is authorized to edit a separate text area. You can switch between users to edit different text parts. The range that is enabled for the current user is highlighted. You can disable the highlighting or customize its color using the corresponding demo’s elements.

Collapse/Expand
Local Copy of this Demo
To inspect the source code for this demo on your machine, you must first install our components via the DevExpress Component Installer.
You can open a local copy of this online demo directly from this webpage (if using v20.2.8, 21.1.4 or higher).
Open CS Solution
Open VB Solution
The source code files for this demo are installed (by default) in the following directories:
\Users\Public\Documents\DevExpress Demos XX.X\Components\ASP.NET\CS\ASPxRichEditDemos
\Users\Public\Documents\DevExpress Demos XX.X\Components\ASP.NET\VB\ASPxRichEditDemos
Tahoma